Portable beverage container systems and methods for adjusting the composition of a beverage

ABSTRACT

A beverage apparatus, the beverage apparatus being hand-holdable by a user of the beverage apparatus to be portable, can include a beverage chamber housing that includes a chamber for storing a consumable liquid. The beverage apparatus can include a dispensing assembly that includes a receptacle. The receptacle can retain a vessel. The vessel can include an electronic tag and can contain an additive. The dispensing assembly can be operatively controllable by a controller to output the additive from the vessel into the consumable liquid. The beverage apparatus can include one or more sensors, devices, or assemblies that can be used to detect a volume of liquid in the chamber or a liquid level in the chamber. The beverage apparatus can include an apparatus computer processor portion (ACP) and an apparatus database portion.

RELATED APPLICATIONS

This application is a continuation of, and claims priority to, U.S.application Ser. No. 16/664,845, filed Oct. 26, 2019, the entiredisclosure of which is hereby incorporated by reference. Such U.S.application Ser. No. 16/664,845 claims priority to U.S. ProvisionalPatent Application Ser. No. 62/900,510 filed Sep. 14, 2019 the entiredisclosure of which is hereby incorporated by reference.

This application is related to U.S. Provisional Patent Application Ser.No. 62/442,039, filed Jan. 4, 2017, the entire disclosure of which ishereby incorporated by reference.

The subject matter of this application is related to U.S. applicationSer. No. 14/960,109, filed Dec. 4, 2015 and published Jun. 9, 2016 (U.S.Publication 2016/0159632 and now U.S. Pat. No. 9,932,217), which claimspriority to U.S. Provisional Patent Application Ser. No. 62/174,935,filed Jun. 12, 2015; U.S. Provisional Patent Application Ser. No.62/174,466, filed Jun. 11, 2015; U.S. Provisional Patent ApplicationSer. No. 62/174,415, filed Jun. 11, 2015; and U.S. Provisional PatentApplication Ser. No. 62/088,189, filed Dec. 5, 2014, the entiredisclosures of which are hereby incorporated by reference. The subjectmatter of this application is also related to International ApplicationSer. No. PCT/US2015/063974, filed Dec. 4, 2015 and published Jun. 9,2016, the entire disclosure of which is hereby incorporated byreference.

The subject matter of this application is related to U.S. applicationSer. No. 15/179,709, filed Jun. 10, 2016, which claims priority to U.S.Provisional Patent Application Ser. No. 62/174,935, filed Jun. 12, 2015;U.S. Provisional Patent Application Ser. No. 62/174,466, filed Jun. 11,2015; U.S. Provisional Patent Application Ser. No. 62/174,459, filedJun. 11, 2015; U.S. Provisional Patent Application Ser. No. 62/174,453,filed Jun. 11, 2015; U.S. Provisional Patent Application Ser. No.62/174,447, filed Jun. 11, 2015; U.S. Provisional Patent ApplicationSer. No. 62/174,427, filed Jun. 11, 2015; U.S. Provisional PatentApplication Ser. No. 62/174,415, filed Jun. 11, 2015; U.S. ProvisionalPatent Application Ser. No. 62/174,343, filed Jun. 11, 2015; U.S.Provisional Patent Application Ser. No. 62/174,336, filed Jun. 11, 2015;U.S. Provisional Patent Application Ser. No. 62/174,254, filed Jun. 11,2015; and U.S. Provisional Patent Application Ser. No. 62/174,440, filedJun. 11, 2015, the entire disclosures of which are hereby incorporatedby reference. The subject matter of this application is also related toInternational Application Ser. No. PCT/US2016/036992, filed Jun. 10,2016 and published Dec. 15, 2016, the entire disclosure of which ishereby incorporated by reference.

BACKGROUND

Portable refillable bottles and other containers used for water andother beverages are widely used and are important for health andhydration. Such bottles and containers are used with increasingfrequency to consume functional ingredients, such as, for example,energy, protein, and sleep supplements. However, one limitation of manyof such bottles and other hydration containers is that the consumablecontents remain constant and unchanged except for changes in quantity asthe contents (frequently, but not exclusively water) are consumed andsubsequently replenished.

Other problems and limitations exist with known bottles, as well as withsystems and methods that are used with such known bottles and othercontainers.

SUMMARY OF THE DISCLOSURE

A beverage apparatus, the beverage apparatus being hand-holdable by auser of the beverage apparatus to be portable, can include a beveragechamber housing that includes a chamber for storing a consumable liquid.The beverage apparatus can include a dispensing assembly that includes areceptacle. The receptacle can retain a vessel.

The vessel can include an electronic tag and can contain an additive.The dispensing assembly can be operatively controllable by a controllerto output the additive from the vessel into the consumable liquid. Thebeverage apparatus can include one or more sensors, devices, orassemblies that can be used to detect a volume of liquid in the chamberor a liquid level in the chamber. The beverage apparatus can include anapparatus computer processor (ACP) and an apparatus database portion.The apparatus database portion can include instructions that areperformed by the ACP in operation of the beverage apparatus. The ACP canbe configured to control the dispensing assembly to perform dispensingof the additive from the vessel into the consumable liquid. The ACP cancommunicate with the electronic tag of the vessel so as to input datafrom and output data to the electronic tag. The ACP can communicate withthe electronic tag to determine state of the additive in the vessel andprocessing can be performed based on the state of the additive in thevessel. The beverage apparatus can include various additional features.Related systems and methods are disclosed.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other objects, features, advantages, and characteristics ofthe present disclosure will become more apparent to those skilled in theart upon consideration of the following Detailed Description, taken inconjunction with the accompanying claims and drawings, all of which forma part of the present disclosure.

In the drawings:

FIG. 1 is a block diagram illustrating an example high-level hydrationecosystem according to principles of the disclosure.

FIG. 2A illustrates a beverage container assembly, according toprinciples of the disclosure.

FIG. 2B is a cross section view of a beverage container assembly,according to principles of the disclosure.

FIG. 3 illustrates a view of a dispensing assembly with a beveragechamber housing removed and with additive vessels, according toprinciples of the disclosure.

FIG. 4A illustrates a bottom view of the dispensing assembly with a basecover removed and with additive vessels, according to principles of thedisclosure.

FIG. 4B illustrates a bottom view of the dispensing assembly with a basecover removed and with additive vessels removed, according to principlesof the disclosure.

FIG. 5A illustrates an isometric perspective view of an additivecontainer, according to principles of the disclosure.

FIG. 5B illustrates a cross section cutaway view of an additivecontainer, according to principles of the disclosure.

FIG. 6 illustrates a cutaway cross section of the dispensing assemblyshowing the operation of a pumping mechanism for an additive container,according to principles of the disclosure.

FIGS. 7A-7C illustrate a cutaway cross section of the dispensingassembly showing the operation of a pumping mechanism for an additivecontainer, according to principles of the disclosure.

FIGS. 8A and 8B illustrate views of a drive mechanism for actuating areceptacle and associated piston of a pumping mechanism, according toprinciples of the disclosure.

FIGS. 9A and 9B illustrate an elevation view of the drive mechanism withthe receptacle in a starting position and in a withdrawn position,respectively, according to principles of the disclosure.

FIG. 10 illustrates a cross section of an internally threaded toothedring engaged with a threaded extension of a pump housing, according toprinciples of the disclosure.

FIGS. 11A-11C illustrate three different cross-sectional cutaway viewsof the dispensing assembly 213, according to principles of thedisclosure.

FIGS. 12A-12B illustrate isometric and cutaway views of a removable cap,according to principles of the disclosure.

FIG. 13 illustrates a cutaway view of a pumping mechanism, according toprinciples of the disclosure.

FIG. 14A illustrates a cutaway view of a receptacle of the embodiment ofFIG. 13, but shown from a different perspective rotated 90 degreesaround a vertical axis, according to principles of the disclosure.

FIGS. 14B and 14C illustrate a seal placed in a shoulder portion of thereceptacle that serves a vacuum breaker function as an additivecontainer is withdrawn from the receptacle, according to principles ofthe disclosure.

FIGS. 15A-15D illustrate different configurations of containers, vesselsor pods for liquid additives that can be used in accordance with variousembodiments.

FIG. 16 illustrates a simplified positive displacement pumping mechanismthat can be used with various actuation mechanisms, according toprinciples of the disclosure.

FIG. 17 is a schematic diagram showing details of a container apparatusor beverage apparatus 300 in an ecosystem 10, according to principles ofthe disclosure.

FIG. 18 is a schematic diagram showing further details of a beverageapparatus 300 in accordance with the principles of the disclosure.

FIG. 19 is a block diagram showing in further detail the apparatuscontroller 350, including an apparatus computer processor (ACP) 360 andapparatus database portion (ADP) 370, according to principles of thedisclosure.

FIG. 19B is a diagram showing further details of a vessel database 374shown in FIG. 19, according to principles of the disclosure.

FIG. 20 is a cross-section schematic diagram showing a beverageapparatus, according to principles of the disclosure.

FIG. 21 is a cross-section schematic diagram showing a beverageapparatus the same as or similar to the beverage apparatus of FIG. 20,according to principles of the disclosure.

FIG. 22 is a schematic diagram of a beverage apparatus the same as thebeverage apparatus or similar to the beverage apparatus of FIG. 21,according to principles of the disclosure.

FIG. 23 is a schematic diagram showing an RFID tag or tag 410 in accordwith the principles of the disclosure.

FIG. 24 is a diagram showing further details of a tag memory portion(TMP) 430 of FIG. 19, according to principles of the disclosure.

FIG. 25 is a high-level flowchart showing details of “additive vesselprocessing is performed, according to principles of the disclosure FIG.26 is a flowchart showing in further detail the apparatus controller 350performs RFID “warnings” processing step 520, as called upon from FIG.23, according to principles of the disclosure.

FIG. 27 is a flowchart showing processing associated with output of datafrom the apparatus controller 350 to the TMP 430, according toprinciples of the disclosure.

FIG. 28 is a flowchart showing processing associated with output of datafrom the TMP 430 to the apparatus controller 350, i.e. from the tag tothe beverage apparatus 300, according to principles of the disclosure.

FIG. 29 is a flowchart showing details of user preference processing,according to principles of the disclosure.

FIG. 30 is a flowchart showing details of user engagement processing,according to principles of the disclosure.

FIG. 31 is a flowchart showing in further detail the apparatus computerprocessor (ACP) 360 performs “expiry” processing step 600, as called onfrom FIG. 23, in accordance with the principles of the disclosure.

FIG. 32 is a flowchart showing details of the “ACP 360 performs productinformation processing” step 610 that is called from FIG. 23, accordingto principles of the disclosure.

FIG. 33 is a flowchart showing details of the “ACP 360 performsapparatus color processing” step 620 as called from FIG. 23 according toprinciples of the disclosure.

FIG. 34 is a flowchart showing in further detail the ACP 360 “performsproduct recall processing” step 630 as called from FIG. 23, according toprinciples of the disclosure.

FIG. 35 is a flowchart showing details of the ACP 360 “dispensingprocessing” step 710 as called from in the processing of FIG. 19,according to principles of the disclosure.

FIG. 36 is a flowchart showing in further detail the ACP 360 performstaste preference processing as called upon from FIG. 33, according toprinciples of the disclosure.

FIG. 37 is a schematic diagram showing a communication assembly 840according to principles of the disclosure.

FIG. 37A is a further schematic diagram showing a communication assemblyaccording to principles of the disclosure.

FIG. 38 is a schematic diagram showing further details of thecommunication assembly 840 mounted on a support platform 808, accordingto principles of the disclosure.

FIG. 39 is a schematic diagram showing details of the communicationassembly 840 and support platform 808, according to principles of thedisclosure.

FIG. 40 is a schematic diagram illustrating further details of theantenna 830, according to principles of the disclosure.

FIG. 41 is a schematic diagram showing further details of thecommunication assembly 840, according to principles of the disclosure.

FIG. 42 is a flowchart showing additive vessel processing, according toprinciples of the disclosure.

FIG. 43 is a flowchart showing processing in which the transceiverperforms processing to interface with the currently connected antenna,according to principles of the disclosure.

FIG. 44 is a diagram illustrating signal strength as it relates toradial distance, according to principles of the disclosure.

FIG. 45 is a diagram illustrating signal strength as it relates to axialdistance, according to principles of the disclosure.

The headings provided herein are for convenience only and do notnecessarily affect the scope or meaning of what is claimed in thepresent disclosure.

In the drawings, same reference numerals and acronyms have been used toidentify same or similar structure, components or functionality for easeof understanding and convenience.

DETAILED DESCRIPTION OF THE DISCLOSURE

A few inventive aspects of the disclosed embodiments are explained indetail below with reference to the various drawing figures. Exemplaryembodiments are described to illustrate the disclosed subject matter,not to limit its scope, which is defined by the claims. Those ofordinary skill in the art will recognize a number of equivalentvariations of the various features provided in the description thatfollows.

In the following description, references are made to various embodimentsin accordance with which the disclosed subject matter can be practiced.Multiple references to “one embodiment” or “an embodiment” do notnecessarily refer to the same embodiment. Particular features,structures or characteristics associated with such embodiments can becombined in any suitable manner in various embodiments. Various examplesand embodiments are described. The following description providesspecific details for a thorough understanding and enabling descriptionof these examples. One skilled in the relevant art will understand,however, that one or more embodiments described herein may be practicedwithout many of these details. Likewise, one skilled in the relevant artwill also understand that one or more embodiments of the presentdisclosure can include many other obvious features not described indetail herein. Additionally, some well-known structures or functions maynot be shown or described in detail below, so as to avoid unnecessarilyobscuring the relevant description.

In at least one embodiment, the present disclosure provides a portable,self-contained beverage apparatus comprising a container assembly havinga known storage capacity for storing a consumable liquid and adispensing assembly. The dispensing assembly can be disposed within thecontainer assembly that dispenses variable, non-zero quantities ofadditives into the consumable liquid stored in the container assembly.The dispensing assembly can include a plurality of apertures structuredand arranged to retain vessels or “pods”. The vessel or pods can containrespective additives to be dispensed into the consumable liquid.

In at least one embodiment, the portable, self-contained beverageapparatus further includes a controller that controls the dispensing bythe dispensing assembly of the variable, non-zero quantities of theadditives into the consumable liquid stored in the container assembly.The controller can include one or more processors and one or moredatabases.

In at least one embodiment, the controller of the portable,self-contained beverage apparatus controls dispensing by the dispensingassembly to maintain a targeted concentration of an additive in theconsumable liquid stored in the container assembly, wherein thecontrolling can be based on tracked consumable liquid level and thequantity of the at least one additive. In at least one embodiment, theportable, self-contained beverage apparatus includes respective vesselsretained, in the plurality of apertures, that contain the additives tobe dispensed into the consumable liquid stored in the containerassembly. The controller of the portable, self-contained beverageapparatus can control dispensing by the dispensing assembly to maintaina desired concentration of an additive in the consumable liquid stored.

Portable hydration containers may be filled in the morning, or othertime of day, and topped-off throughout the day as liquid is consumed. Itcan be neither practical nor desirable to require that a user fillmultiple compartments of a container with multiple different consumableliquids or mixtures for consumption throughout the course of the day. Itis also not desirable to require a user to carry around separateadditive vessels—and to insert additives contained therein into ahydration container when needed by the user. Therefore, a more practicaland desirable solution is to dispense a selection, sequence orcombination of different additives from one or more additive vesselsinto a consumable liquid at the appropriate time in response to a signalor signals. The signal can be from the beverage apparatus and/or from amobile or wearable device, processor or application that is associatedwith the beverage apparatus. Such arrangement can be used in conjunctionwith various other features and functionality.

The “beverage apparatus” as disclosed herein can also be described as a“bottle” or “container assembly” of the disclosure. The beverageapparatus, bottle, or container assembly can include variousfunctionality as described herein.

Accordingly, one or more embodiments of the present disclosure relate toa consumable container having a dispensing module assembly with a numberof apertures into which additive vessels can be inserted by a user. Eachof these additive vessels can have an RFID tag attached to the vessel.An RFID transceiver can be mounted on the dispensing assembly or otherstructure of the beverage apparatus so as to interface with the RFIDtag—and specifically with an antenna of the RFID tag. The RFIDtransceiver can including a reader, an antenna, and/or other elementsfor communicating, including writing and reading, with one or more RFIDtags on the vessels. The RFID transceiver, on the dispensing assembly,can be mounted on a surface of a dispensing module located on a centralaxis of the consumable container. In other embodiments, a plurality ofRFID transceivers can be provided and each RFID transceiver (of thedispensing assembly) can be positioned in a respective staticrelationship relative to a respective RFID tag (on a respective additivevessel that is inserted into the beverage apparatus). The arrangementcan provide access to data about the contents of the additive vesselfrom the RFID tag of the additive vessel. The methods, systems, andapparatuses of the disclosure can be designed to access various dataabout the contents of an additive vessel. One having ordinary skill inthe art will recognize that a passive data system such as RFID may beideal due to its passive nature, read/write capability, and low-cost.However, other functionality, arrangements, and methods could providesimilar results, including but not limited to physical key-basedmethods, or optical methods. As will be described in greater detailbelow, the methods, systems, and apparatus of the present disclosure canbe designed to present information to a user regarding the additivesconsumed and/or vessel(s) inserted in the beverage apparatus. Forexample, according to principles of the disclosure, the portablecontainer may display (e.g., on a user interface screen of thecontainer) information or generate an alert to the user when one or moreof the additive vessels inserted in the beverage apparatus is, or willsoon become empty. In another example, the container may be configuredto predict a future date when one or more of the additive vesselsinserted in the beverage apparatus will become empty. Such a featureserves to recommend and/or automate future purchases. Such a systemmight also function to adjust or otherwise modify dispensing protocol toensure that the additive does not become depleted on or before atargeted time.

In accordance with at least one embodiment, the methods, systems, andapparatuses may be designed to provide for direct or indirectcommunication of an instruction from a central control application to acontainer assembly. Such a direct or indirect communication may be, forexample, an instruction to dispense an additive, may include adispensing schedule and/or protocol, or may indicate that an additive(e.g., medication, pharmaceutical, or the like) has, or has not, beendispensed by the dispensing apparatus within the container. Dataassociated with the dispensing event (or lack thereof) might also becollected and communicated directly or indirectly between the dispensingdevice and the aforementioned central control application. In accordancewith at least one embodiment, Bluetooth low energy may be used as theprimary transmission method of such data. However, other transmissiontechnology, channels and/or protocols can be used to providecommunication between a vessel and a container assembly.

Also disclosed herein are methods and apparatuses for the precise andcontinuously variable dispensing of a removable additive vessel throughthe use of a discretely adjustable piston or actuator. Adjustment of adispensed additive can be provided by a variable stroke length of thepiston or actuator. Such adjustment can be controlled by a user—such asthrough a sequence of buttons pressed on a user interface. For example,a particular button can be associated with a dispense of a particularadditive/additive vessel. As the user's finger is held on the particularbutton a longer amount of time, the dispense can be extended thusdispensing more additive. The arrangement can provide a dispensing eventthat is precise and repeatable. Passive electronics or other electronicsmeasuring which additive vessel, dispensing quantity, and how manydispensing events are initiated can log the user's consumption activityand behaviors.

Embodiments of some or all of the methods disclosed herein may berepresented as instructions embodied on transitory or non-transitoryprocessor-readable storage media such as optical or magnetic memory orrepresented as a propagated signal provided to a processor or dataprocessing device via a communication network. The communication networkcan be, for example, an Internet or telephone connection, or othercommunication channel. FIG. 1 shows an illustrative diagram of anoverall ecosystem or system 10, according to principles of thedisclosure. FIG. 1 includes a beverage apparatus 100 that can beportable. The beverage apparatus 100 can be hand-holdable by a user soas to provide portability. The beverage apparatus 100 can contain aconsumable (e.g., a liquid) into which liquid, powder, and/or otherforms of consumable additives may be dispensed from one or more separateremovable additive vessels 101. Data about the additives within eachadditive vessel 101 may be encoded within an RFID or similar active,passive, or other type tag 102 mounted on or otherwise attached oraffixed to or associated with the additive vessel 101. Such data aboutthe additives contained within the additive vessel or vessel 101 can beread from the RFID or similar type tag 102 by, for example, an RFIDtransceiver with antenna that is a component of the beverage apparatus100. For example, in accordance with at least one embodiment, thebeverage apparatus 100 may include an RFID antenna (not shown in FIG. 1)that rotates around or that is positioned around a central axis of thebeverage apparatus 100 to individually and/or sequentially read datafrom the additive vessels 101. The additive vessels 101 can be insertedin a circular arrangement around the central axis of the beverageapparatus. In other embodiments, a plurality of RFID readers or RFIDtransceivers can be provided and each RFID reader can be static relativeto a respective RFID tag (on a respective additive vessel). There can beone or more than one additive vessel 101. Data about the additivescontained in the additive vessels 101, can be collected, analyzed,and/or communicated by the beverage apparatus 100 (e.g., by a processorand/or other components of the beverage apparatus 100), and madeavailable to one or more user devices 106, local data storage 105,remote data storage 107, and other data resources, such as dataanalytics processor 109. Such information may be presented to the userusing a display 111 mounted on the beverage apparatus 100 and/or using adisplay on the user device 106. The user device 106 can be a cell phoneor smart phone, for example. Communications may be performed or providedbetween the various components of the system 10 over a network 108. Thenetwork 108 may be provided using a cloud based architecture or othernetwork.

FIGS. 2A and 2B illustrate a beverage apparatus 200, in accordance withat least one embodiment, that will be shown in further detail insubsequent FIGS. 3-12 and described in the description that follows. Aswill be understood by one skilled in the art, the various features andfunctionality described above and elsewhere in this disclosure can beapplied, combined and used in conjunction with the beverage apparatus200 in accordance with the various embodiments described below. Thebeverage apparatus 200 may be of similar or same construction as thebeverage apparatus 100 of FIG. 1. The beverage apparatus 200 can includea controller 210 that controls operations of the beverage apparatus 200.

FIG. 2A illustrates a perspective view while FIG. 2B illustrates a crosssection cutaway view of the beverage container assembly or beverageapparatus 200, according to principles of the disclosure. The beverageapparatus 200 includes a beverage chamber housing 214, which forms aportion of a chamber 230 to contain a beverage. The beverage chamberhousing 214 can be configured with an open threaded base that threadsonto a top end of a dispensing assembly 213. A top portion of thedispensing assembly 213 can include a platform 217, which can form abottom half or portion of the chamber 230 to contain the beverage. Thedispensing assembly 213 can house one or more containers of additives,i.e. vessels of additives, to be dispensed into the chamber 230, adispensing mechanism or dispensing assembly configured to control theaddition of the additives from the vessels, and electronics configuredto control the dispensing mechanism. A removable base cover 220 can beconfigured to thread on to and off of a bottom end of the dispensingassembly 213 in order to provide access so as to insert and removecontainers or vessels of additives. As described herein, each of thesecontainers of additives can be referred to herein as an additive vessel,a vessel, or a “pod” 250, as shown in FIGS. 4A, 5A and 5B, for example.

As shown in FIG. 2A, the beverage apparatus 200 includes a top end 201and a bottom end 202. It should be appreciated that the variousillustrative drawings of embodiments of the disclosure are shown in anupright orientation and in various illustrative drawings of embodimentsof the disclosure are shown in an upside down or inverted orientation.Accordingly, labeling of top end and bottom end are provided forclarity.

The beverage apparatus 200 can include a removable cap 212, which, inthe illustrated embodiment, seals a top opening of the beverage chamberhousing 214 to complete the chamber 230. The cap 212 can be configuredto thread or snap onto a top end of the beverage chamber housing 214.Referring to FIG. 2B, in one embodiment, the cap 212 can include acompressible bladder 231 formed of silicone or other suitable rubber ormaterial, that allows for deformation of the bladder so as toaccommodate the addition of liquid additives into the chamber 230 by thedispensing assembly 213. The cap 212 also includes an air passageway 232to allow air to escape from behind the bladder 231 so that the bladdercan compress to accommodate the addition of the liquid additives.

Referring to FIG. 2A, the dispensing assembly 213 can be furtherconfigured with a user interface 222, which can include a display 211and one or more user input buttons 216. In the illustrated embodiment ofFIG. 2, the display 211 includes five LEDs (light-emitting diodes), withthree LEDs in a triangle that can be configured to indicate selection ofone of three additive vessels. Another LED can be configured to indicatea power on or wake up condition of the dispensing assembly, and yetanother LED that can be configured to indicate that a dispensing of anadditive to the beverage chamber housing 214 has been selected. The LEDsmay use specific lensing or may be embedded behind a micro-perforatedmaterial to abstract the user from the physical components of the LEDs.In one embodiment, a single user input button can be configured as amulti-function button to perform different actions depending on theamount of pressure applied to it by the user, by duration of press(es),sequence or pattern of presses, and/or by quantity of presses, forexample. The button of the buttons 216 can also be configured toaccommodate partial or complete depression of the button, which can bedifferentiated by a perceptible detent or click, for example. Sucharrangement can provide further varied functionality. The user interface222 can provide an arrangement for the user to, for example, dispense anadditive from an additive vessel or display the current battery level ofthe system and apparatus.

FIG. 3 illustrates a view of the dispensing assembly 213 with thebeverage chamber housing 214 removed. A top portion of the dispensingassembly 213 includes an annular wall with threads 240 that engage withmatching threads on the beverage chamber housing 214. The top portion ofthe dispensing assembly 213 can also include the platform 217 to form abase for the beverage chamber housing 214 in order to contain thebeverage within the chamber 230. The platform 217 can include one ormore outlet ports 241 through which additives are added to the beveragein the chamber, and in the illustrated embodiment of FIG. 3, three (3)such ports 241 are shown. In one embodiment, each port 241 can be sealedby a one-way valve 242 (e.g. an umbrella valve of rubber or silicone)that permits one-way passage of a liquid additive into the chamber fromthe vessel. As will be discussed below, each one-way valve 242 can formpart of a pumping mechanism 260 (FIG. 6) that injects liquid additivesinto the chamber. In one embodiment, the pumping mechanism 260 can be areciprocating positive displacement pump. FIG. 3 also illustrates anultrasonic fluid level sensor 218 disposed on or within the platform217. In accordance with one embodiment, the fluid level sensor 218 uses“round trip time” for a reflected sound wave(s) to measure the height ofa fluid or water column within the chamber 230 and thereby infer ordetermine fill volume. Other arrangements can be used to sense level ofliquid in a container assembly of the disclosure.

FIGS. 4A and 4B illustrate a bottom view of the dispensing assembly 213with the base cover 220 removed. FIG. 4A shows the ends of each of threeadditive vessels 250 that are threaded into three correspondingreceptacles or apertures 245 as shown in FIG. 4B. While the term“receptacle” is used in the description that follows, for the purpose ofconsistency with various embodiments described above, the receptacles245 can also be referred to as “apertures” 245.

FIGS. 5A and 5B illustrate a perspective view and a cross sectioncutaway view, respectively, of an additive vessel 250 in accordance withone embodiment. FIG. 5A shows a top end 258 of the additive vessel 250and a bottom end 259 of the additive vessel 250, as such additive vesselwould be positioned in routine use in a container assembly or beverageapparatus, such as is shown in FIG. 2A. The additive vessel 250 caninclude a housing or body 251, which can be cylindrical in shape to fitinto a corresponding cylindrically shaped receptacle or aperture 245 andengage with threads 246. At a first end or proximal end, the housing 251can be covered with a cap 252 with threads 254. The cap 252 can besnapped or clicked onto the housing 251. The cap 252 can be integrallyformed with the housing or body 251 of the vessel 250. The threads 254of the vessel 250 can be provided on the housing or body 251. Thethreads 254 of the vessel 250 can be provided on any portion or surfaceof the vessel and/or connected structure so as to secure the vessel 250into a respective receptacle 245.

The threads 254 can engage with threads or receiving threads 246 in areceptacle 245 so as to lock the additive vessel 250 into place withinthe dispensing assembly 213. At a second end or distal end, the vessel250 can include a piston head 253 that includes a port 255 that iscapped or closed by a one-way valve 256 (e.g. an umbrella valve ofrubber or silicone). The port 255 and one-way valve 256 function topermit additive to flow in only one direction from the vessel 250, i.e.out of the additive vessel and into a pumping chamber 261 of the pumpingmechanism 260, as shown in FIG. 6 and described below.

Referring to FIG. 5B, a slideable plunger 257 is disposed within aninterior or interior surface 251′ of the housing 251. The interior 251′of the housing 251 and the exterior of the plunger 257 can be a matchingcylindrical shape such that the plunger 257 can slide along the lengthof the housing 251, from a first end to the second end of the housing,as additive contained within the housing is dispensed from the vessel.The plunger 257 is preferably formed of soft plastic such as LDPE (lowdensity polyethylene) that seals against the interior of the housing andmoves so that no air is allowed into the vessel 250 during dispensing ofthe additive.

FIGS. 6 and 7A-C illustrate a cutaway cross section of the dispensingassembly showing the operation of the pumping mechanism 260 for anadditive vessel 250. FIG. 6 shows an enlarged view of a portion of FIG.7B showing the pumping mechanism 260 in a partially actuated state,according to principles of the disclosure. As illustrated, the vessel250 is threaded into the receptacle 245 such that the piston head 253 ofthe vessel 250 engages or mates with the housing of the receptacle 245to form or provide a piston 265. The piston 265 can slide back and forthwithin a pumping chamber 261 formed by a cylinder 262 of a pump housing264. As described above, the piston head 253 includes a one-way valve256 that permits flow from the vessel 250 into the pumping chamber 261.At an opposite end or top end of the chamber 261 from the piston head253, the second one-way valve 242 permits liquid additive to flow fromthe pumping chamber 261 into the beverage chamber 230 as the piston 265moves forward, i.e. downward as shown in the inverted arrangement ofFIG. 6, in the cylinder 262.

FIG. 7A shows the receptacle 245 and piston 265 in a starting positionand the plunger 257 of the additive vessel 250 in an initial positionprior to any additive being dispensed from a “full” additive vessel 250.As shown in FIG. 7B, the piston 265 is withdrawn, and the one-way valve242 at the outlet port 241 blocks fluid flow in the reverse direction,creating a vacuum which draws fluid from the additive vessel 250 throughthe one-way valve 256 into the pumping chamber 261. It should be notedthat in FIG. 7B, the plunger 257 has moved from its starting positionillustrated in FIG. 7A to accommodate fluid flow from the vessel 250into the pumping chamber 261. As shown in FIG. 7C, the piston 265 isdriven back to its starting position, compressing the fluid within thechamber 261 and forcing the fluid through the one-way valve 242 at theoutlet port 241 (see FIG. 3) and into the beverage chamber 230. Theone-way valve 256 blocks the flow of fluid from returning into thevessel 250. Positive pressure, accordingly, is produced in thiscompression stroke, dispensing the contents of the pump chamber 323through the outlet port 241 into the beverage chamber 230.

The volume dispensed during a single piston stroke can be modulatedlinearly by modifying the piston stroke length. Multiple piston strokescan be used to dispense larger quantities. By design, the volume of thepumping chamber can be configured to be as small as practically possiblewhen the piston 265 is in the starting position to avoid wastingadditive liquid when a depleted additive vessel is withdrawn from thereceptacle.

FIGS. 8A and 8B illustrate views of a drive mechanism 270 for actuatingthe receptacle 245 and associated piston 265 of the pumping mechanism260. FIG. 8A illustrates an internal perspective view of the dispensingassembly 213 without an outer cover. FIG. 8B illustrates an additionalinternal perspective view of the dispensing assembly 213, with structureremoved, to better illustrate certain aspects of the drive mechanism270. As illustrated, each receptacle 245 and its associated piston 265(not visible in FIGS. 8A-B) is moved down and up by an internallythreaded toothed ring 271. A set of internal threads 272 on eachinternally threaded toothed ring 271 can engage with a threadedextension 276 (FIG. 9B) of the pump housing 264. Gears 271′ on the outerdiameter of each internally threaded toothed ring 271, can be driven bya gear 273, which in turn can be driven by an optional gearbox 274,which in turn is driven by an electric motor 275.

FIGS. 9A and 9B illustrate an elevation view of the drive mechanism withthe receptacle in a starting position (9A) and in a withdrawn position(9B). As the toothed ring 271 rotates, the internal threads 272 causethe toothed ring to rise and fall on the threaded extension 276 of thepump housing 264. The receptacle 245, which can be snapped into oradhered to or integral with the toothed ring 271, also therefore risesand falls with the toothed ring, causing the piston 265 to move withinthe cylinder 262. In accordance with one embodiment, the threads on thetoothed ring 271 and the threaded extension 276 can be a “fast” 4-startthread that cause the toothed ring 271 to travel to full linearextension with 180 degrees of rotation. The threads can be configured tohave an ACME profile or similar. FIG. 10 illustrates a cross section ofan internally threaded toothed ring 271 engaged with a threadedextension 276 (FIG. 9B) of the pump housing 264.

FIGS. 11A-11C illustrate three different cross sectional cutaway viewsof the dispensing assembly 213.

FIGS. 12A and 12B illustrate isometric and cutaway views of theremovable cap 212. As discussed above with reference to FIG. 2, in theillustrated embodiment, the cap 212 seals a top opening of the beveragechamber housing 214 to complete the chamber 230. The cap 212 can beconfigured to thread or snap onto a top end of the beverage chamberhousing 214. The cap 212 includes a compressible bladder 231 formed ofsilicone or other suitable rubber, that allows for deformation of thebladder 231 so as to accommodate the addition of liquid additives (fromthe vessel 250) into the chamber 230 by the dispensing assembly 213. Thecap 212 also includes an air passageway 232 to allow air to escape frombehind the bladder 231 so that the bladder can compress to accommodatethe addition of the liquid additives. As shown in FIGS. 12A-B, thebladder 231 can be configured with a dimpled dome shape that yields anapproximately linear resistance to deformation.

FIG. 13 illustrates a cutaway view of a pumping mechanism 280 inaccordance with one embodiment of the disclosure. Similar to theembodiments discussed above with reference to FIGS. 2-12, an additivevessel 281 is received into a receptacle 282, which engages within apump housing 283. Two one-way valves similarly work together with asliding piston and cylinder to pump additive liquid through a pumpingchamber. In the embodiment illustrated in FIG. 13, however, thereceptacle 282 can be actuated manually, by a user grasping andwithdrawing the receptacle from the pump housing 283, or by anothermechanical means. The receptacle 282 is withdrawn against pressure of aspring 284, which is biased to press the receptacle back to its startposition, such that when the receptacle is released, any additive fluiddrawn into the pumping chamber is then automatically ejected into thebeverage chamber.

FIG. 14A illustrates a cutaway view of the receptacle 282 of theembodiment of FIG. 13, but shown from a different perspective rotated 90degrees around a vertical axis. The receptacle 282 includes a tab 285that can be used either manually or actuated by a mechanism in order towithdraw the receptacle against the tension of the spring 284 from thepump housing 283. FIG. 14A also shows the additive vessel 281 removedfrom the receptacle 282.

FIGS. 14B and 14C illustrate a seal 286 placed in a shoulder portion ofthe receptacle 282 that serves a vacuum breaker function as the additivevessel 281 is withdrawn from the receptacle, in an embodiment accordingto principles of the disclosure. Once the additive vessel 281 iswithdrawn even a slightest amount, the vessel no longer contacts theseal 286 and therefore air is allowed to pass into the pumping chamberarea as the vessel is withdrawn. If no air were allowed to pass into thepumping chamber, the action of withdrawing the vessel or additive vesselwould create a vacuum that would suck additive fluid out of the vesseland into the now open pumping chamber. FIGS. 15A-D illustrate differentconfigurations of additive vessels, containers or pods for liquidadditives that can be used in accordance with various embodiments. FIG.15A illustrates an airless or non-vented rear load vessel 15A with arigid tubular side wall. The additive vessel of FIG. 15A is similar infunction to the vessel 250 illustrated in FIGS. 5A-B, with a plunger 257that moves to prevent air from entering the vessel. FIG. 15B illustratesan airless front load vessel 15B with a rigid tubular side wall. FIG.15C illustrates a collapsible bag or sachet 15C enclosed within an outercontainer 15C′. The collapsible bag makes the plunger unnecessary,according to an embodiment of the disclosure. FIG. 15D illustrates avented additive vessel 15D, which allows air to pass back into thevessel to take the place of pumped additive fluid. A two-way valve 290allows additive fluid to pass out of the vessel through a center portionof the valve, while air is allowed to enter the vessel through ports 291around the periphery of the valve and under an umbrella portion of thevalve.

FIG. 16 illustrates a simplified positive displacement pumping mechanism16A that can be used with various actuation mechanisms in accordancewith various embodiments.

One benefit of the foregoing described positive displacement pumpconfigurations is that when the additive vessel is withdrawn and whenthe beverage chamber housing is removed from the dispensing assembly allparts of the pumping mechanism become visible and accessible forcleaning. The pumping chamber is accessible through the receptacle andonly a one-way umbrella valve, for example, sits in the port between thepumping chamber and the platform which is otherwise also accessible forcleaning. A one-way umbrella valve can be easily removed and cleaned orreplaced.

As noted above, the various features and functionality of theembodiments described above with reference to FIG. 1, FIGS. 2-12, andfurther with respect to FIGS. 13-16, can be combined as desired. Ingeneral, various features and functionality of the embodiments describedherein can be combined and used in conjunction with various features andfunctionality of other embodiments.

For example, the dispensing assembly 213 illustrated in FIG. 3 can befurther configured with an attachment sensor that monitors whether thebeverage chamber housing 214 is threaded onto the dispensing assembly213 before a dispensing event occurs. An attachment sensor can replaceor supplement a lid sensor and checks can be performed before initiatinga dispensing event. Each additive vessel can be configured with an RFIDtag. The RFID tag of each additive vessel, once in the beverageapparatus 200, can be associated with a respective RFID reader ortransceiver that is mounted on the dispensing assembly 213 or on anotherportion of the beverage apparatus 200. In the various embodiments ofFIGS. 2-16, each vessel can be configured with its own separate pumpingmechanism 260.

As shown in FIG. 8A, for example, the beverage apparatus 200, as well asthe other container assemblies described herein, can include variousstructural platforms, connectors, fasteners, support posts, and otherstructure. The beverage apparatus 200 can include an upper supportplatform 207 and a lower support platform 208. The lower supportplatform 208 can be positioned below or lower than the upper supportplatform 207 when the bottle is in an upright orientation. Additionally,the beverage apparatus 200 can include a bottom support platform 209.Each of the support platforms 207, 208, 209 can provide structuralsupport and integrity to the beverage apparatus 200. For example, thelower support platform 208 can support the controller 210. For example,the bottom support platform 209 can support the controller 210. Forexample, the lower support platform 208 can support the controller 210.The support platforms 207, 208, 209 can be connected and/or adjoined bycolumns, flanges, or other support structure.

FIG. 17 shows a beverage apparatus 300, according to principles of thedisclosure. The beverage apparatus 300 can be part of an ecosystem orsystem 10′. The beverage apparatus 300 can be similar in structure andfunctionality to the beverage apparatus 100 described herein. Thebeverage apparatus 300 can be similar in structure and functionality tothe beverage apparatus 200 described herein. The beverage apparatus 300can include any of the features of the beverage apparatus 100 and/or thebeverage apparatus 200 as may be desired.

As shown in FIG. 17, the beverage apparatus 300 can include a beveragechamber housing 315, a base cover 317 and a dispensing assembly 318. Thedispensing assembly 318 can be positioned between the beverage chamberhousing 315 and base cover 317. The beverage chamber housing 315 caninclude an internal volume or chamber 316. The internal volume orchamber 316 can hold or contain the consumable liquid that is containedin the beverage apparatus 300.

The dispensing assembly 318 can be provided with a display or interface310 that includes various user interface features, such as buttons orlights. The interface 310 and/or other user interface features can beprovided anywhere on the beverage apparatus 300 as may be desired. Anynumber of user interface features can be provided so as to afforddesired user control or functionality, so as to effectively control andmonitor status of the beverage apparatus 300, and so as to provideinterface between the beverage apparatus 300 and the user and/or userdevice 106. An additive button 313 can be provided on the beverageapparatus 300 and an illustrative function button 314 can be provided toafford functionality as described herein. In accordance with at leastone embodiment of the disclosure, a user can press the additive button313 so as to dispense additive, from a pod, additive vessel or vessel400, into the consumable liquid contained in the beverage apparatus 300.The beverage apparatus 300 can include pod indicator lights 311. The podindicator lights 311 can be provided to represent or show which pod isselected to dispense an additive and/or which pod is dispensing anadditive. For example, each of the pod indicator lights 311 can beassociated with a respective pod 400, i.e. additive vessel 400, in thebeverage apparatus 300. When a user presses and/or holds the additivebutton 313, the selected pod 400 (as indicated by one of the podindicator lights 311) can dispense the desired additive. The particularpod 400 (that the user wishes to select) can be selected, by the user,through a predetermined sequence of presses of the additive button 313,for example. It is appreciated that the disclosure is not limited to thebuttons, lights, and/or other user interface devices shown in FIG. 17.Rather, other user interface arrangements, features or functionality maybe utilized so as to control dispensing of additives from a pod and/orother operations of the beverage apparatus 300. The interface lights 312can provide the user with various status information regarding thebeverage apparatus 300. Functionality and/or operational control, forexample, that is provided via the interface 310 can also be provided viaa user device 106, such as a cell phone 106, for example. The userdevice 106 can communicate with the beverage apparatus 300 as otherwisedescribed herein. As shown in FIG. 17, the beverage apparatus 300 caninclude an apparatus controller or controller 350. The apparatuscontroller 350 can include an apparatus computer processor (ACP) 360(the ACP 360 may also be described as an apparatus processing portion(APP) 360) and an apparatus database portion (ADP) 370. The ACP 360 caninclude one or more processors. The apparatus database portion 370 caninclude various computer memory that includes various databases, datarecords, memory portions and other memory architecture. Accordingly, theapparatus database portion 370 can be provided with computer readableinstructions that the ACP 360 can read according to principles of thedisclosure. Based on such instructions and/or other data, the ACP 360can perform various operations and/or provide functionality as describedherein.

The apparatus controller 350, with the ACP 360 and the apparatusdatabase portion 370, can control or provide for operations of thebeverage apparatus 300 and can provide the various features andfunctionality described herein. Various wires, communication pathsand/or other conductive paths (not shown) can be utilized so as toprovide connectivity between the apparatus controller 350, variousmotors or other drive mechanisms of the beverage apparatus 300 and/orother components of the beverage apparatus 300. Such wires,communication paths or other conductive paths can be in the form ofinsulated wires and/or structurally embedded wires or electricalconduits that are routed between components. Such wires or otherconductive paths can be integrated into one or more components of thebeverage apparatus 300. Such wires or other conductive paths can providefor both communication between components and/or electrical power to (orbetween) components, for example.

The ACP 360 can be in communication with the user device 106 that isassociated with the particular user of the beverage apparatus 300, otheruser devices 106, a cloud network or resource 108, and/or other systemsand/or other networks. For example, the beverage apparatus 300 can be incommunication with a cell phone 106, of the user, that is associatedwith the beverage apparatus 300. The apparatus database portion 370 cancontain any of a wide variety of data utilized by or generated by theapparatus controller 350 and/or the ACP 360, such as described below.

The beverage apparatus 300, as shown in FIG. 17, can also include anexternal communication portion or communication portion 359 thatprovides communication between the beverage apparatus 300 and variousother components of the system 10′. For example, the communicationportion 359 can provide communication with a user device such as a usercell phone 106. The apparatus controller 350 and/or the ACP 360 canperform a wide variety of processing related to the dispensing ofadditives and other processing as otherwise described herein.

The controller or apparatus controller 350 can be fully provided withinthe beverage apparatus 300. Accordingly, the beverage apparatus 300 canoperate fully independently, with all processing and datastorage/retrieval performed onboard the beverage apparatus 300, withoutexternal input/output. On the other hand, processing and datastorage/retrieval can be shared between the onboard apparatus controller350 and external computing resources. Such external resources mightinclude the ecosystem server or server 20. The server 20 can includeprocessors and databases that can be utilized in conjunction withoperation of the controller 350. The server 20 can interface withnumerous other beverage apparatuses 300 and user devices 106 in theecosystem 10′. Such numerous beverage apparatuses 300 and devices 106may be in the thousands or millions. Additionally, the server 20 itselfcan be dispersed over a cloud architecture or dispersed over otherarchitecture that includes numerous processing resources and numerousdatabase resources.

As shown in FIG. 17, the beverage apparatus 300 can include the pod,additive vessel, or vessel 400. The vessel 400 can be removable, by theuser in routine use, from the beverage apparatus 300 in accordance withone or more embodiments of the disclosure. The vessel 400 can beassociated with or include a tag or RFID tag 410. The tag 410 can bemounted to or on a side of the vessel or mounted to some other locationor position on the vessel 400. The tag 410 can be mounted on a lower orbottom surface 403 of the vessel 400. The vessel 400 and tag 410 caninclude and/or be combined with any of the features described above withreference to the beverage apparatus 100 and/or the beverage apparatus200, for example. In manner described above, the vessel 400 isinsertable into the beverage apparatus 300. The vessel 400 can dispenseadditive, which is contained in the vessel 400, in manner as describedabove.

FIG. 18 is a schematic diagram showing further details of a beverageapparatus 300 in accordance with the principles of the disclosure. Thebeverage apparatus 300 can include the dispensing assembly 318 and basecover 317 as described above. The dispensing assembly 318, in thebeverage apparatus 300, can include an upper support platform 307.Beverage apparatus 300 can also include a lower support platform 308 anda bottom support platform 309. Supports 309S can extend between thelower support platform 308 and the upper support platform 307 and thebottom support platform 309. Accordingly, the upper support platform 307can be structurally supported by the supports 309S. Various otherstructural supports, flanges, and/or connections between components canbe provided. As shown in FIG. 18, the beverage apparatus 300 can includea pod aperture or vessel aperture 389 that is provided in a receptacle390. The receptacle 390 may be described as a “bay” or as a “vesselbay”. The vessel 400 can be slid into and disposed in the pod aperture389 in the receptacle 390 in manner as described herein. The vessel 400can include a piston head 405 and a port 406, which can be provided witha one-way valve 407 to allow additive to exit the vessel 400. The pistonhead 405 can be of same or similar structure—and function in same orsimilar manner—as the piston head 253 with port 255, as described above.The piston head 405 can be positioned under the upper support platform307 of the beverage apparatus 300. Mechanical components within or ofthe beverage apparatus 300 can be the same or similar to the mechanicalcomponents described above to provide dispensing of additive from thevessel 400 into the internal volume 316 of the beverage apparatus. Inmanner described above, the internal volume or chamber 316 can contain aconsumable liquid. As shown in FIG. 18, the vessel 400 can include thetag or RFID tag 410 that is provided on a bottom surface 403 of thevessel 400. For example, the RFID tag 410 can be adhesively attached thebottom surface 403.

With reference to FIG. 20 and FIG. 21, the receptacle 390 can include areceptacle wall 391 that defines aperture 389. The receptacle wall 391can include a first reduced neck portion 392. The receptacle wall 391can also include a second reduced neck portion 394. An annular abutmentshoulder 393, of the receptacle 390, can connect the reduced neckportions 392, 394. The receptacle 390 can include a top edge 395. Thetop edge 395 can constitute a part of the piston 405-390. With sucharrangement, the piston 405-390 can be described as being “radiallybisected”.

The receptacle 390 can include a seating engagement structure 396. Thestructure 396 can be in the form of an annular flange or shoulder thatextends downwardly from the second reduced neck portion or portion 394,the annular abutment shoulder 393, and/or a junction of the elements394, 393. The seating engagement structure 396 can engage with anannular abutment shoulder 419 of the vessel 400.

Relatedly, the vessel 400 can include a vessel body 417. The vessel 400can include a neck 418. The neck 418 can be defined by the annularabutment shoulder 419. The neck 418 can be engaged with, i.e. slid into,the second reduced neck portion 394 of the receptacle 390. Sucharrangement can provide securement of the vessel 400 within thereceptacle 390.

As otherwise described herein, the receptacle 390/vessel 400 canreciprocate as a unit so as to provide a pumping arrangement or pumpingmechanism. Relatedly, the second reduced neck portion 394 can beprovided with an O-ring annular groove 397. An O-ring 398 can bedisposed in the O-ring annular groove 397. The O-ring 398 can provide aseal between the receptacle 390 and a cylinder 324, i.e. while stillproviding or allowing reciprocating movement of the receptacle 390within the cylinder 324. That is, the arrangement can provide a sealwhile still providing for pumping action.

As shown in FIG. 20, the vessel 400 can include a vessel cap or cap 451.As shown in FIG. 20, the vessel cap 451 can be provided with a hole 452.The hole 452 allows air to pass into the interior of the vessel 400 soas to allow advancement of a plunger 409, i.e. so as to not create anundesired vacuum within the interior of the vessel 400. The vessel cap451 of the pod or vessel 400 can be a separate piece relative to thebody 417 of the vessel 400. The vessel cap 451 can be integrally formedwith body 417.

It is appreciated that the beverage apparatus 300 can accommodatemultiple pods or vessels 400. Accordingly, the arrangement of FIG. 18can also include vessel 400′ with tag 410′, i.e. a second tag 410′ thatis on the vessel 400′, whereas a first tag 410 is on the first vessel400. Beverage apparatus 300 can include functionality so as to engagewith the second vessel 400′ in similar or same manner as the beverageapparatus 300 engages with the vessel 400, i.e. the first vessel 400. Acontroller of the beverage apparatus can communicate with the secondvessel 400′ via antenna 342′.

As shown in FIG. 18, the beverage apparatus 300 can include a controlleror apparatus controller 350. The apparatus controller 350 can controloperations of the beverage apparatus 300. The apparatus controller 350can include the apparatus computer processor (ACP) 360. The apparatuscontroller 350 can also include the apparatus database portion (ADP)370. The apparatus controller 350 can be in the form of a physicalmachine or control unit that is physically attached to a suitablestructural component of the beverage apparatus 300. For example, asshown in FIG. 18, the apparatus controller 350 can be attached to theupper support platform 307. The apparatus controller 350 can be inelectronic communication with a reader, an RFID reader, RFID transceiveror transceiver, i.e. such as through wiring. The apparatus controller350 can be in communication with an RFID transceiver 341, which can beor include an RFID reader. The RFID transceiver 341 can be in electroniccommunication with an antenna 342, i.e. such as through wiring. In someembodiments, such components can be integrated together. For example,the apparatus controller 350 can include the RFID reader 341 and theantenna 342. The antenna 342 can be disposed in the structure of thebeverage apparatus 300 so as to be sufficiently proximate to the RFIDtag 410, i.e. so as to effectively provide communications between theantenna 342 and the RFID tag 410 of the pod or vessel 400. For example,the antenna 342 can be integrated into or provided upon or affixed tothe lower support platform 308 and/or the bottom support platform 309,as schematically illustrated in FIG. 18. The RFID transceiver 341 orreader 341 and the antenna 342 can collectively constitute an RFIDtransceiver assembly 340.

To accommodate a second vessel 400′, the beverage apparatus 300 can alsoinclude a second antenna 342′. The second vessel 400′ can be removablypositioned in a further or second vessel receptacle 390′, i.e. thereceptacle 390 can be described as a first receptacle 390. Accordingly,it is appreciated that the beverage apparatus 300 can include one ormore vessels 400, including vessel 401′, that are received into thebeverage apparatus 300. Each of such vessels 400 can include a tag orRFID tag 410. Each of the tags 410, affixed to a respective vessel 400,can be associated with a respective antenna 342 that are each incommunication with the RFID reader or transceiver 341. In turn, the RFIDtransceiver 341 can be in communication with the apparatus controller350. In some embodiments, the beverage apparatus 300 can includemultiple readers. In such embodiment, each of such transceivers 341 canprovide support, be connected and/or communicate with a respectiveantenna 342, 342′ (for each tag/vessel 400, 400). In some embodiments, asingle RFID transceiver 341 can provide support, be connected and/orcommunicate with a single antenna 342, and such single antenna 342 cancommunicate with one or the plurality of tags 410 (on respective vessels400). The single RFID transceiver 341 can be rotatable, such as via apivoting mechanism, so as to directed toward a particular pod/RFID tagof such pod.

FIG. 19 is a block diagram showing in further detail the apparatuscontroller 350, including the ACP 360 and apparatus database portion370, that can be provided in the beverage apparatus 300, according toprinciples of the disclosure. The ACP 360 can include a generalprocessing portion 361. The general processing portion 361 can handle avariety of processing performed by the beverage apparatus 300 that isnot performed by other specialized processing portions as describedherein. The general processing portion 361 can coordinate, orchestrate,and/or control more specialized processing that is performed by thespecialized processing portions.

Various specialized processing portions can be provided in the ACP 360.The ACP 360 can include a dispense processing portion 362. The dispenseprocessing portion 362 can perform a wide variety of operationsassociated with dispense of an additive from a vessel 400 that isdisposed in the beverage apparatus 300. Such operations associated withdispense of an additive from a vessel 400 are described herein.

The ACP 360 can also include a liquid level processing portion 363. Theliquid level processing portion 363 can perform a wide variety ofoperations associated with determining liquid level of the beverageapparatus. In general, it is appreciated that the various processingportions of the ACP 360 can perform with each other and/or complementeach other so as to provide functionality of the beverage apparatus 300.

The ACP 360 can also include an interface processing portion 364. Theinterface processing portion 364 can perform various operations relatingto interface functionality of the beverage apparatus 300. For example,the interface processing portion 364 can observe operations of thebeverage apparatus 300 and output representative data to the user viathe interface 310. In general, the interface processing portion 364 caninput data from or via the display or interface 310, such as datagenerated from interface with a user, and control operations of the ACP360 based on such input data. The interface processing portion 364 canobserve operations of the beverage apparatus 300 and output data via theinterface 310 so as to represent operations that are performed by thebeverage apparatus 300. The interface processing portion 364 can providesimilar functionality between the beverage apparatus 300 and a user viaa user device 106. Accordingly, the interface processing portion 364 canoutput data to the device 106 so as to represent operations of thebeverage apparatus 300. The interface processing portion 364 can inputdata from the user device 106 that results from interface with the user.Such input data, from the user device 106, can dictate or controloperations of the beverage apparatus 300. As otherwise described herein,the ACP 360 and the controller 350 in general can be disposed fullywithin the beverage apparatus 300. Portions of the ACP 360/controller350 can be disposed external to the beverage apparatus 300. That is, itis appreciated that some processing performed might be performed by aserver 20, the user device 106 and/or other processing resource, forexample, in communication with the ACP 360 and/or controller 350.

As shown in FIG. 19 and FIG. 18, the controller 350 can also include theapparatus database portion 370. The apparatus database portion 370 caninclude a general database 371. The general database 371 can store awide variety of data that is used by or generated by the ACP 360. Theapparatus database portion 370 can also include a user database 372. Theuser database 372 can include a wide variety of data regarding theparticular user of the beverage apparatus 300 and data regarding otherusers that are associated with the beverage apparatus 300 in somemanner. The user database 372 can include user preference information,user history information, use pattern information, use trendinformation, as well as other data regarding use of the beverageapparatus 300 by a user (or users). The user database 372 can includedata regarding the user device 106 and communication particulars of theuser device 106 such as communication credentials, for example.

As described herein, information and data have been utilized hereininterchangeably, unless otherwise provided by the particular context.

The apparatus data portion 370 can also include a liquid level database373. The liquid level database 373 can store various data utilized by orgenerated by the liquid level processing portion 363. Operations of theliquid level processing portion 363 are further described below.

As described above, FIG. 20 is a cross-section schematic diagram showingdetails of a beverage apparatus 300. The beverage apparatus 300 caninclude a dispensing assembly 318 that can include structure similar tothe structure (of the dispensing assembly 213) described above withreference to FIGS. 6 and 7A-C, for example. The dispensing assembly 318can be provided between the beverage chamber housing 315 and the basecover 317. In some embodiments of the disclosure, the dispensingassembly 318 can include the base cover 317. FIG. 21 is a cross-sectionschematic diagram showing details of a beverage apparatus or bottle 300the same as or similar to the beverage apparatus of FIG. 20. In FIG. 21,the receptacle 390, with vessel 400 therein, has been lowered so as tobe withdrawn from the outlet port 321. Accordingly, the volume of thepumping chamber 323 is increased.

In manner similar to that described above, the dispensing assembly 318can include a dispense mechanism or pumping mechanism 319—to dispenseadditive from the additive vessel 400. The pumping mechanism 319 caninclude a pump housing 320, a toothed ring assembly or toothed ring 330,and a receptacle 390, in accordance with at least some embodiments ofthe disclosure.

The additive vessel 400 can include an internal volume or volume 404.FIG. 20 shows the receptacle or vessel 400 in what might be described asa “starting” position with no or little liquid in a pumping chamber orchamber 323. The vessel 400 can include the plunger 409. The plunger 409as shown in FIG. 20 (in contrast to an initial position illustrated inFIG. 7A) is about half-way into the vessel 400, i.e. showing that abouthalf of the additive has already been dispensed from the internal volume404 (of the vessel 400) shown in FIG. 20. The arrangement, including theposition of the plunger 409 shown in FIG. 20, could follow a dispenseevent, or in the example of FIG. 20, likely a series of dispense events.

As illustrated in FIG. 20, the receptacle 390 can include or defineaperture 389. The vessel 400 can be threaded and positioned into thereceptacle 390 such that piston head 405 of the vessel 400 is positionedin and/or forms a part of pumping chamber 323. The piston head 405 canprovide, at least in part, a piston 405-390. Such “piston” 405-390, inaccordance with at least one embodiment of the disclosure, can includethe piston head 405 (of the vessel 400) and an upper end or top edge 395of the receptacle 390. The receptacle 390 can support the vessel 400 viathreads 399 (of the receptacle 390) engaging threads 408 (of vessel400). As the receptacle 390 moves up and down (by operation as describedherein), so does the vessel 400. Accordingly, the receptacle 390 movablysupports the vessel 400. The “piston” 405-390 can slide back and forth(i.e. up and down as shown in FIG. 20) within the pumping chamber 323.The pumping chamber 323 can be formed in part by a cylinder 324 of pumphousing 320. As described above, the piston head 405 (of the vessel) caninclude a one-way valve 407. The one-way valve 407 permits flow ofliquid from the vessel 400 into the pumping chamber 323. At a top end ofthe chamber 323 (above the piston head 405) is the further or secondone-way valve, i.e. the one-way valve 322 associated with the pumphousing 320. The one-way valve 322 permits liquid additive to flow fromthe pumping chamber 323 into the chamber 316 as the piston 405-390 movesupward (from the position shown in FIG. 21 to the position shown in FIG.20) in the cylinder 324.

The pump housing 320 can be supported within or on the upper supportplatform 307, as shown in FIG. 18. For example, the pump housing 320 caninclude or be a round or circular insert that includes an annularseating flange 326. Such annular seating flange 326, of the pump housing320, can be adhesively bonded or heat bonded into a mating aperture 307Ain the upper support platform 307. The annular seating flange 326 can befrictionally fit into the mating aperture 307A such that the pumphousing 320 might be “switched out” if desired, i.e. switched with areplacement housing 320.

As shown in FIG. 20 and FIG. 21, the piston 405-390 and vessel 400 canbe drawn down—while the one-way valve 322 (at the outlet port 321)blocks fluid flow from coming into the pumping chamber 323 from thechamber 316. As a result, a vacuum is created that draws fluid from theadditive vessel 400 through the one-way valve 407 into the pumpingchamber 323. Accordingly, such manipulation provides for additive to bepassed into the pumping chamber 323—and such additive “queued” to bedispensed into the beverage chamber 316. Such arrangement of thebeverage apparatus 300 is similar to the arrangement shown in FIG. 7B.

Then, the piston 405-390 can be driven back to its starting position(FIG. 20) so as to compress or force the fluid, in the chamber 323,through the one-way valve 322 at the outlet port 321 and into thebeverage chamber 316. The one-way valve 407 (of the vessel 400) blocksthe flow of fluid/additive from returning into the vessel 400. Positivepressure, accordingly, is produced in what can be described as a“compression stroke”. Such compression stroke results in dispensing thecontents of the pump chamber or pumping chamber through the outlet port321 into the beverage chamber 316. Such process can be described as a“single piston stroke.”

The volume dispensed from the pumping chamber 323 during such a singlepiston stroke can be modulated linearly by modifying the piston strokelength, i.e. how much the piston moves up and down in the arrangement ofFIG. 20 and FIG. 21. Multiple piston strokes can be used to dispenselarger quantities. By design, the volume of the pumping chamber 323 canbe configured to be as small as practically possible when the piston405-390 is in the starting position, as shown in FIG. 20, to avoidwasting additive liquid when a depleted additive vessel 400 is withdrawnfrom the receptacle.

FIG. 20 also shows a dispense mechanism or pumping mechanism 319 foractuating the receptacle 390 with associated piston 405-390 of thepumping mechanism 319. As illustrated, the receptacle 390 and itsassociated piston 405-390 can be moved down and up by operation of thetoothed ring assembly 330. Such arrangement is the same or similar toarrangements described above.

That is, the dispense mechanism 319 can include a pump housing 320. Thepump housing 320 can include a cylinder 324 and a threaded extension325. The toothed ring assembly 330 can include a set of internal threads332. The internal threads 332 can engage with the threaded extension 325of the pump housing 320. The threaded extension 325 can be in the formof threads on an outer diameter of the cylinder 324 of the pump housing320, in accordance with at least some embodiments of the disclosure. Thetoothed ring assembly can include an annular abutment shoulder 333. Theannular abutment shoulder 333 can engage with the receptacle 390 as thereceptacle 390 is moved upward as shown in FIG. 21 so as to limit upwardmovement, in an embodiment.

The toothed ring assembly 330 can include teeth 331 on an outer diameter(OD) of the toothed ring assembly 330. As shown in FIG. 20, the teeth331 can be vertically oriented or aligned. Each toothed ring assembly330, can be driven by a gear 337 (shown in cross section in FIG. 20).That is, the teeth 331 can be driven by the gear 337. The gear 337 canbe driven by a motor 338. Other gears and/or a gearbox can be interposedbetween the gear 337 and the motor 338 (and/or between the gear 337 andthe toothed ring assembly 330) so as to provide a desired gear ratio.The position of the vessel 400 shown in FIG. 20 can be described as astarting position. By operation of the dispense mechanism or pumpingmechanism 319, the vessel 400 can be displaced downward, as shown inFIG. 21, into a withdrawn position.

The motor 338 and gear 337 can rotate the toothed ring assembly 330. Asthe toothed ring assembly 330 rotates, the internal threads 332 causethe toothed ring assembly 330 to rise and fall on the threaded extension325 of the pump housing 320. The receptacle 390, which can be snappedinto or adhered to or integral with the toothed ring assembly 330, alsotherefore rises and falls with the toothed ring assembly 330, causingthe piston 405-390 to move within the cylinder 324. More specifically,the piston 405-390 can move within an inner diameter surface (i.e. areceptacle engagement sleeve portion) 334 of the cylinder 324. Inaccordance with one embodiment, the threads 332 on the toothed ringassembly 330 and the threaded extension 325 can be a “fast” 4-startthread that cause the toothed ring assembly 330 to travel to full linearextension with 180 degrees of rotation. The threads can be configured tohave an ACME profile or similar profile.

In accordance with at least some embodiments of the disclosure, thereceptacle 390 can be frictionally secured within the toothed ringassembly 330. Accordingly, as the toothed ring assembly 330reciprocates, as a result of being driven by the teeth 331, thereceptacle 390 reciprocates with the toothed ring assembly 330. Thevessel 400 can be threaded onto or into the receptacle 390. Accordinglythe vessel 400 can reciprocate with the receptacle 390. In accordancewith at least some embodiments of the disclosure, the toothed ringassembly 330, the receptacle 390, and the vessel 400 can reciprocate asa unit, i.e. reciprocate so as to move or oscillate between the startposition and a withdrawn position as a unit. In at least someembodiments, the receptacle 390, or structure connected thereto, can beasymmetrical in shape. Such asymmetry in shape can be provided so as topreclude rotation of the receptacle or pod as the pod is beingreciprocated, such as between the positions shown in FIG. 20 and FIG.21. For example, the receptacle can be provided with ridges or fins thatrun along the length of the receptacle—and that engage with matchinggrooves or slots in a structure of the beverage apparatus that isstatic, i.e. that does not reciprocate. Accordingly, the reciprocationbetween the positions of FIG. 20 and FIG. 21 can be provided for, whilepreventing rotation of the vessel or pod. In other embodiments, the pod400 and receptacle 390 may be allowed to rotate in conjunction withreciprocation of the pod.

In manner similar to that described above, as shown in FIG. 20, thevessel 400 can be provided with threads 408. The receptacle 390 can beprovided with threads 399. The threads 408 can be provided on anyportion or outer surface of the vessel so as to secure the vessel 400into the receptacle 390—so long as such threads 408 are provided tomatch or mate with threads on the receptacle 390. The threads 399 can beprovided on any portion or inner surface of the receptacle 390 so as tosecure the vessel 400 into the receptacle 390—so long as such threads399 (of the receptacle) are provided to match with threads on the vessel400.

The vessel 400 can be attached to the receptacle 390 in other manners ascompared to the particulars shown in FIG. 20. For example, the vessel400 can include threads around the top of the vessel 400, such as onneck 418, that engage with threads on an inner diameter of the secondreduced neck portion 394 of the receptacle 390. For example, the vessel400 can include threads around the top of the vessel 400 that engagewith threads on an inner diameter of the first reduced neck portion 392of the receptacle 390. Other thread arrangements can be provided.Hereinafter, various features relating to level sensing will bedescribed according to principles of the disclosure. As described above,a beverage apparatus can contain a consumable liquid that contains anadditive. The consumable liquid can be contained in a chamber of thebeverage apparatus. A controller of the beverage apparatus can controldispensing of the additive, by a dispensing assembly, so as to maintaina targeted concentration of the additive in the consumable liquid and/orso as to attain a desired concentration of the additive in theconsumable liquid. The controller can utilize a variety of data in thedispensing of the additive. Such data can be input from a variety ofsources. One type of data that may be input and utilized by thecontroller can include data that relates to a level or liquid level ofthe consumable liquid in the beverage apparatus or bottle.

For example, a fluid sensor or fluid level sensor may be in the form ofan ultrasonic device or ultrasonic sensor. The fluid level sensor canemit a sound wave. A portion of the sound wave can be returned as aresult of encountering a top surface of the consumable liquid in thechamber. Accordingly, the fluid level sensor can use “round trip time”for the reflected sound wave or waves to measure the height of a fluidor water column within the chamber. Based on the height of the fluidcolumn within the chamber, the controller can be provided with knowndata so as to determine, i.e. calculate based on diameter or shape forexample, the fill volume of the chamber. According to principles of thedisclosure, a function or lookup table can be used to match or “map” theobserved height of the liquid in the beverage apparatus, i.e. thebottle, to the particular volume that corresponds to such liquid height.As described below, various arrangements and processes can be used tosense level of liquid in a beverage apparatus/bottle of the disclosure.

Hereinafter, various features relating to level sensing, i.e. liquidlevel sensing, will be further described. The liquid level sensingdescribed herein can be performed in the environment of any of thebeverage apparatuses as described herein, as may be desired. Forexample, liquid level sensing can be performed in the environment of thebeverage apparatus 300 shown, for example, in FIGS. 20 and 21. Forpurposes of illustration of level sensing, FIG. 22 is a schematicdiagram of a beverage apparatus 300 the same as or similar to thebeverage apparatus 300 of FIGS. 20 and 21.

As shown in FIG. 22, the beverage apparatus 300 can include a beveragechamber housing 315. The beverage chamber housing 315 can include aninternal volume or chamber 316. A consumable liquid with additive can becontained in the chamber 316. The beverage apparatus 300 can include aremovable cap 315C. A user can remove the removable cap 315C so as tofill the beverage apparatus 300 with liquid. The beverage apparatus 300can also include a base cover or base cap 317. The base cover 317 can beremoved by a user so as to switch out or insert a vessel or pod 400 intothe dispense mechanism 319. In accordance with at least someembodiments, a dispensing assembly 318 can be described as including thedispense mechanism 319 and the vessel 400. As shown in FIG. 22, thevessel 400 can include a lower or bottom surface 403. A tag, RFID tag,or electronic tag 410 can be mounted on the bottom surface 403. Thevessel 400 can be of same or similar structure, and can be manipulatedin similar manner, to that described above with reference to FIGS. 20and 21, for example.

The beverage apparatus 300 as shown in FIG. 22 can also include variousstructural features including those described above. The beverageapparatus 300 can include an upper support platform 307, a lower supportplatform 308, and a bottom support platform 309. The support platforms307, 308, 309, as described herein, can serve to provide structuralintegrity to the beverage apparatus 300 and to support variouscomponents of the beverage apparatus. As described herein, the uppersupport platform 307 can support, at least in part, the dispensemechanism 319. As shown in FIG. 22, the lower support platform 308 canserve to support an apparatus controller 350.

However, it should be appreciated that the controller 350 can also besupported by the upper support platform 307 or by some other supportstructure within the beverage apparatus.

The controller 350 can include the apparatus computer processor (ACP)360 of FIG. 19. The controller 350 can include an apparatus databaseportion (ADP) 370. The ACP 360 and the ADP 370 can include variousfeatures as described herein. The ADP 370 can control the variousoperations of the beverage apparatus 300. The ADP 370 can store datathat is utilized by the ACP 360 and/or data that is generated by the ACP360. Accordingly, the ADP 370 can store various instructions that areutilized by the ACP 360 in performing the various operations describedherein. With regard to level sensing, the apparatus controller 350 canalso contain and/or be in communication with various sensors,mechanisms, devices, gadgets, systems, and/or apparatus, which cancollectively be described as “elements” 351. One element 351 can be anultrasonic sensor 353, i.e. an ultrasonic device 353, as shown in FIG.22. The ultrasonic sensor 353 can be connected to the controller 350utilizing a suitable communication pathway 357. The ultrasonic device orultrasonic sensor can be provided with its own computer processingportion or processor. The communication pathway 357 can be in the formof a wire, cable, wireless link, embedded wire that is embedded instructure of the beverage apparatus 300, embedded cable, laminatedcable, laminated wire, laminated conductive pathway, or othercommunication pathway. The communication pathway(s) 357 can be providedbetween any of the elements described herein and/or the controller 350and can provide communications so as to provide control of a particularelement and/or can provide power to a particular element. The beverageapparatus or bottle can include one or more power sources, such as oneor more batteries 354, that can power the various components of thebeverage apparatus.

The beverage apparatus 300 can also include other elements 351. Theother elements 351 can include a clock 352. The clock 352 can performvarious operations associated with the passage of time. The clock 352can, in a routine manner, track time including days, hours, minutes,seconds, milliseconds, etc. The clock 352 can also perform variousrelated functions including stopwatch operations, determining a durationof time, determining when a particular time has been attained,determining a differential between two observed times, and otheroperations. In at least some embodiments of the disclosure, thecontroller 350 can also perform such operations. That is, in someembodiments, the clock 352 can be limited to simply outputting timevalues to the controller 350—and the controller 350 performing variousoperations based on such output time values. For example, a time valuethat is output by the clock 352 might be 09102019day101521 hour todenote Sep. 10, 2019 at 10:15:21 AM. It should be appreciated that thecontent, nature, and format of such data can be varied as desired. Theclock 352 can be in the controller 350 and/or be a part of thecontroller 352. As shown in FIG. 22, the controller 350 can also includeone or more batteries or other power source 354. For example, thebattery 354 can be a rechargeable battery that can be recharged byattaching the battery 354 to an external power source. The battery 354can power the various components of the beverage apparatus.

The elements 351 can include an accelerometer 355. The accelerometer 355can monitor acceleration of the beverage apparatus 300 in the x-y-zspace and output representative data to the controller 350. The elements351 can also include an angle sensor 356. The angle sensor 356 canmonitor an angle at which the beverage apparatus 300 is positioned. Eachof the elements 351 can perform processing of data that is then outputto the controller 350 and/or the elements 351 can output unprocessed orraw data to the controller 350. In the latter case, the controller 350can process such raw data so as to generate requisite information. Forexample, the angle sensor 356 can, itself, perform processing to outputan angle such as 51°. On the other hand, the angle sensor 356 can outputraw data and the controller 350 determine the angle based on the rawdata. According to at least one embodiment of the disclosure, theaccelerometer can sense or determine angle of the beverage apparatus300. In accordance with at least some embodiments, the angle sensor 356can be or include the accelerometer 355. The accelerometer 355 can be orinclude an angle sensor 356.

Additionally, the elements 351 provided in the beverage apparatus 300can include one or more temperature sensors. The temperature sensors caninclude a liquid temperature sensor 305 and an apparatus temperaturesensor 306. The liquid temperature sensor 305 can be provided in oradjacent to the chamber 316 so as to be exposed to the consumable liquidin the beverage apparatus 300. Accordingly, a temperature of theconsumable liquid in the beverage apparatus 300 can be determined by theliquid temperature sensor 305. The apparatus temperature sensor 306 canbe provided within structure of the beverage apparatus 300 so as tomeasure an operating temperature of the beverage apparatus. Theapparatus temperature sensor 306 can be provided on or exposed to anexterior wall of the beverage apparatus 300 so as to input an ambienttemperature in which the beverage apparatus 300 is disposed. Multipletemperature sensors can be utilized so as to input both internaloperating temperature of the beverage apparatus as well as ambienttemperature of the beverage apparatus. Such various temperature sensingcan be utilized in operation of the beverage apparatus as describedherein.

Hereinafter, further features of disclosure will be described withreference to FIG. 18. As shown in FIG. 18, the beverage apparatus 300can include a vessel, pod, or additive vessel 400. The vessel 400 caninclude a tag 410. The tag 410 can be an RFID tag. The tag 410 can be incommunication with the transceiver 341 (of the beverage apparatus) viaan antenna 342. The beverage apparatus 300 can include one or morevessels 400. The vessels 400 can include a second vessel 400′. Thesecond vessel 400′ can include a second tag or second RFID tag 410′ Thebeverage apparatus 300 can also include one or more antennas 342. Theantennas 342 can include a second antenna 342′. The second antenna 342′can provide communication between the second tag 410′ (of the secondpod) and the transceiver 341.

The second vessel 400′ can be removably positioned in a second vesselreceptacle 390′. Accordingly, it is appreciated that the beverageapparatus 300 can include one or more vessels 400, including vessel401′, that are received into the beverage apparatus 300. Each of suchvessels 400 can include a tag or RFID tag 410. Each of the tags 410,410′ affixed to a respective vessel 400, can be associated with arespective antenna 342, 342′ that are each in communication with theRFID reader or transceiver 341. In turn, the reader or transceiver 341can be in communication with the apparatus controller 350. In someembodiments, the beverage apparatus 300 can include multipletransceivers 341. In such embodiment, each of such transceivers 341 canprovide support, be connected and/or communicate with a respectiveantenna 342, 342′ (for each tag/vessel 400). In some embodiments, asingle transceiver 341 can provide support, be connected and/orcommunicate with a single antenna 342, and such single antenna 342 cancommunicate with the plurality of tags 410 (on respective vessels 400).

As shown in FIG. 18 and described above, the beverage apparatus 300 caninclude vessel 400 with RFID tag or tag 410. Relatedly, FIG. 23 is aschematic diagram showing an RFID tag 410 in accord with the principlesof the disclosure. As shown, the RFID tag 410 can include a tagprocessing portion (TPP) 420 and a tag memory portion (TMP) 430. The tagprocessing portion 420 can be in the form of or include an integratedcircuit and/or other processing component. The TMP 430 can be in theform of or include a computer readable medium. The tag 410 can alsoinclude a suitable substrate or tag structure 411. For example, the tagstructure 411 can be a plastic plate, filament, sheet, or otherstructure that can be provided to support the various components of theRFID tag 410. The tag 410 can include an antenna 412. The tag 410 can bean RFID tag. In some embodiments, components of the electronic tag 410can be integrated into the vessel 400 or pod 400. In such arrangement,structure of the vessel or pod 400 would provide or constitute the tagstructure or substrate 411. Additionally, it is appreciated thatcomponents of the tag 410 can be distributed on different parts orportions of the vessel 400. For example, the antenna 412, of the tag410, might be provided on a bottom or lower surface of the vessel 400. Amemory portion 430, i.e. TMP 430, of the tag 410 might be provided on afirst side of the vessel 400, and the tag processing portion 420 mightbe provided on an opposing second side of the vessel 400. For example,the tag processing portion 420 and/or TMP 430 can be provided proximateto or at a halfway point between the top of the vessel 400 and thebottom of the vessel 400 as shown in FIG. 17. Such components might beswitched out, exchanged in position, and changed in position as may bedesired.

Accordingly, the principles of the disclosure are not limited to theparticular arrangement as shown in FIG. 23 or FIG. 18. The antenna 412is illustratively shown in a spiral configuration running outwardly fromthe tag processing portion 420 to an outer periphery of the tagstructure 411. However, various other antenna structure can be utilizedas dependent on various factors, such as the particular arrangement ofthe respective antenna 342 (of the beverage apparatus 300) thatinterfaces with the tag antenna 412.

As described above, FIG. 19 is a block diagram showing in further detailthe apparatus controller 350, including the ACP 360 (apparatus computerprocessor 360) and apparatus database portion 370, that can be providedin the beverage apparatus 300, according to principles of thedisclosure. In addition to the components described above, the ACP 360can also include an RFID processing portion 366 or a tag processingportion 366. The tag processing portion 366 can perform a wide varietyof operations associated with outputting data to the tag 410, inputtingdata from the tag 410, processing based on data from the tag 410, andvarious related processing. The tag processing portion 366 can performoperations and provide functionality in conjunction with the operationof the dispense processing portion 362. In general, it is appreciatedthat the various processing portions of the ACP 360 can perform witheach other and/or complement each other so as to provide functionalityof the beverage apparatus 300 as described herein.

As shown in FIG. 19, the controller 350 can include an apparatusdatabase portion 370, as described above. The apparatus data portion 370can also include a tag database 376 or RFID database 376. The tagdatabase 376 can contain data used by or generated by the tag processingportion 366. The tag database 376 can store various data utilized by orgenerated by the beverage apparatus 300. For example, the tag database376 can store data regarding communication protocols, security data,encryption data, and other data relating to communication between one ormore vessels 400 and the controller 350.

The tag database 376 can also include a vessel_1 database 377—to supportand hold data regarding a first pod or first vessel 400 that is disposedin the beverage apparatus. The vessel_1 database 377 can store variousinformation related to the first vessel that has been inserted into thebeverage apparatus 300, i.e., so as to dispense additives containedtherein into the internal volume or chamber 316. For example, thevessel_1 database 377 can contain data regarding the vessel 400described herein. The tag database 376 can also include a vessel_2database 378. The vessel_2 database 378 can contain data regarding afurther vessel 400′ that has been placed into the beverage apparatus300. Illustratively, such further vessel is illustrated in FIG. 18 asthe vessel 400′. Other databases and/or memory sections can be providedin an arrangement in which the beverage apparatus 300 is structured toretain more than the two vessels 400, 400′.

FIG. 19B is a diagram showing further details of the vessel_1 database377 shown in FIG. 19, according to principles of the disclosure. Itshould be appreciated that the vessel_1 database 377 can be part ofand/or integrated into a larger database, such as the apparatus databaseportion 370, using a relational database architecture or otherarrangement. As shown, the vessel_1 database 377 (in the tag database376) can include a plurality of tag data records 381. The tag datarecords 381 can be associated with other data in the apparatus databaseportion 370 utilizing any suitable architecture, such as relationaldatabase architecture. Each of the tag data records 381 can include arecord identifier field 382 and a content field 383. For purposes ofillustration, the record identifier field 382 contains simple numericalindicia. However, it should be appreciated that the record identifierfield 382 can include more complex numerical and/or alphanumericalindicia so as to be associated with other data in the apparatus databaseportion 370 and so as to assist in reading and writing data from thevessel_1 database 377. The various data illustrated in FIG. 19B,provided in the vessel_1 database 377, will be described in furtherdetail in the processing described below.

FIG. 24 is a diagram showing further details of the tag memory portion(TMP) 430 described above. The TMP 430 can be provided on or in thevessel 400. The TMP 430 can include a plurality of tag data records 431.The tag data records or data records of an RFID tag (or other electronictag) that is mounted on or in a pod/vessel can be described asfunctional data records—since such data records can provide a variety offunctionality as described herein. The tag data records 431 can eachinclude a record identifier field 432 and a content field 433. Forpurposes of illustration, the record identifier field 432 containssimple numerical indicia. However, it should be appreciated that therecord identifier field 432 can include more complex numerical and/oralphanumerical indicia so as to be associated with other data in the tagdata record 431 and so as to assist in reading and writing data from thetag memory portion 430. Various data is illustratively shown in the TMP430. Such data in the TMP 430 can relate to various attributes of theparticular vessel 400 to which the tag 410 is attached. Such data in theTMP 430 can include manufacturer information of the particular vessel,additive information, historical information, use information, contentinformation, and security information, as well as various otherinformation as shown, for example. In particular, the TMP 430 caninclude data regarding the state of the vessel 400. Further detailsregarding the data stored in the TMP 430 are described below in thecontext of processing of the beverage apparatus 300, according toprinciples of the disclosure.

The beverage apparatus 300 can perform a wide variety of processing soas to provide a beverage, with desired additives and of desiredcomposition, to the user. As described above, such processing caninclude the control of dispensing from one or more vessels 400 into aliquid in the internal volume or chamber 316 of the beverage apparatus300. Relatedly, the beverage apparatus 300 can perform variousprocessing relating to the data stored in the beverage apparatus 300 anddata stored in the vessel 400. Such processing can include the readingand writing of data from and to the tag 410 of the vessel 400.

FIG. 25 is a high-level flowchart showing details of “data record (DR)processing” step 500 that is performed by the beverage apparatus 300and/or the vessel 400, according to principles of the disclosure. Inparticular, such processing can include processing performed byapparatus controller 350 that includes the ACP 360.

As illustratively shown in FIG. 25, the processing can begin in step 500and pass to step 501 and/or step 511. In step 501, the apparatuscontroller 350 (AC) performs processing to determine if a new vessel hasbeen inserted into the beverage apparatus 300. For example, suchprocessing can include a button or other mechanism that might bereleased when a vessel 400 is removed from the pod aperture 389 and thatis again depressed when a new vessel 400 is inserted into the vesselaperture 321. Other techniques can be utilized to determine if a newvessel 400 has been inserted into (or removed from) the beverageapparatus 300. For example, the apparatus controller 350 mayelectronically detect a new electronic signature or other characteristicor attribute of a different tag 410 that has been inserted (on thedifferent vessel 400). For example, an antenna on either an RFID tag (ona pod) or an antenna integrated with the receptacle can sense or detecta disruption in an observed electronic field. The disruption may be avariance in observed inductance, for example. An antenna on the bottlemay identify a disruption in observed inductance as a result of the RFIDtag and/or the RFID antenna (of a pod) being disposed in the receptacle.As shown in FIG. 25, once the apparatus controller 350 detects that anew vessel 400 has been inserted, i.e. yes in step 501, the processpasses to step 502. In step 502, various processes can be called upon orinvoked by the apparatus controller 350. The processes of step 502 caninclude processes to identify various attributes of the vessel 400 thathas been inserted, for example. Step 502 can be characterized as“additive vessel interface processing” or “pod interface processing”.

In accordance with embodiments of the disclosure, various othermechanisms or techniques can be used to identify or determine if a pod(be it a new pod or a previously used pod) has been inserted into thebeverage apparatus 300.

For example, a photo sensor or light sensor can be used to detect thepresence of a pod in the beverage apparatus 300. The light sensor candetect a change in observed light as a result of a pod being removedfrom the beverage apparatus or as a result of a pod being inserted intothe beverage apparatus. The light sensor can detect the differential inlight caused by such change in pod disposition—and communicate suchdisposition to the apparatus controller 350. For example, a receptacle390 can be provided with the light sensor on one side of the receptacleand a light source on an opposing side of the receptacle. Insertion of apod into the receptacle can result in variance in intensity of lightreceived by the light sensor from the light source, i.e. as a result ofthe presence of the pod between the light source and the light sensor.Based on this observation that is communicated to the apparatuscontroller 350—the apparatus controller 350 can assume that suchvariance is attributable to a pod being inserted into the particularreceptacle. Processing can then be performed based on such observation.

The controller and associated transceiver, of a beverage apparatus, maycommunicate with or interrogate an electronic tag of a pod, such as anRFID tag of a pod, in a periodicity or manner as desired. Thecontroller/transceiver may interrogate a pod on an ongoing basis, suchas every one second, every two seconds or at some other periodicity orpattern, e.g., as may be desired. The controller/transceiver mayinterrogate a pod only upon a predetermined event(s) being observed—suchas the insertion of a pod, a dispense event, a fill event, or some otherevent. Further, interrogation can include a combination of interrogatingbased on a certain periodicity/pattern and interrogating based onobserving a particular event. Interrogation might be performed in acertain periodicity after a particular event is observed.

Further, a beverage apparatus of the disclosure can include one or moresensors to detect relative position of components of the beverageapparatus. For example, a Hall effect sensor in conjunction with one ormore magnets can be used to detect whether or not the base cover 317(see FIG. 22) is on the dispensing assembly 318. That is, a magnet maybe provided in the base cover 317 and a Hall effect sensor provided inthe dispensing assembly 318, so as to sense proximity of the base cover317. In an embodiment, a pod might be provided with a magnet and asensor (e.g. a Hall effect sensor) detect presence or non-presence ofthe magnet in the pod. A Hall effect sensor can be used in sucharrangements. The Hall effect sensor can include a device that canmeasure a magnetic field. That is, an output or observed voltage orcurrent of the Hall effect sensor can be proportional to a magneticfield or magnetic field strength passing through the Hall effect sensor.A magnet proximate to the Hall effect sensor can vary the magnetic fieldor magnetic field strength, which is observed by the Hall effect sensor.Thus, the Hall effect sensor can detect the presence of the magnet. Sucharrangement can be utilized to determine proximity or connection of anyof the components of the beverage apparatus as described herein, as maybe desired. A Hall effect sensor 890 is illustratively shown in FIG. 38.Such Hall effect sensor can interact with a magnet on or in base cover317, for example. For example, a user might be required to open a doorto insert a pod into the beverage apparatus, and such door can beprovided with a magnet. Such magnet can interact with a Hall effectsensor on an adjacent portion of the beverage apparatus. The Hall effectsensor can be positioned so as to vary in distance from the magnetdepending on whether the door is opened or closed. Thus, the Hall effectsensor/controller can detect whether the door has been opened/closed,which is indicative of a new pod being inserted via the door. Theprocessing illustrated in step 502, is not limited to the particularsituation in which a vessel 400 has been inserted into the beverageapparatus 300. Rather, other scenarios can result in the apparatuscontroller 350 invoking the processing of step 502. For example, suchother scenarios can include the beverage apparatus 300 beingdisconnected from power, a sudden acceleration or deceleration, asdetected by an accelerometer, such as from a drop of the beverageapparatus 300, a malfunction of the tag 410 and/or upon the depletion orcomplete depletion of additive in the vessel 400.

As shown in FIG. 25, the apparatus controller 350 can perform RFID basedwarnings processing, as illustrated by step 503. The apparatuscontroller 350 can perform expiry processing as illustrated by step 504.The apparatus controller 350 can perform product information processingas illustrated by step 505. The apparatus controller 350 can performproduct color processing as illustrated by step 506. The apparatuscontroller 350 can perform product recall processing as illustrated bystep 507.

In accord with embodiments of the disclosure, the various processingdescribed in step 502 can be performed in a different order as comparedto that illustrated in FIG. 25. The various processing described in step502 can be performed in a parallel manner to each other. The variousprocessing described in step 502 can be performed in a serial manner, inan order as desired. Each of such respective processes illustrated instep 502, can be performed by respective subroutines as described indetail below. In some embodiments, settings of the beverage apparatus300 (i.e. the apparatus controller 350) can be configured to perform allof the processes of step 502 upon a vessel 400 being inserted into thebeverage apparatus 300. On the other hand, settings of the beverageapparatus 300 can be configured so as to only perform some of theprocesses of step 502 upon a vessel 400 being inserted into the beverageapparatus 300.

Relatedly, FIG. 25 shows step 511. In step 511, the ACP 360 performsprocessing so as to determine if a dispense has been requested by theuser. For example, step 511 can monitor for input from the user that isindicative of a dispense having been requested, which might include abutton of the beverage apparatus or bottle 300 being depressed.Additionally, the processing of step 511 can include or utilize one ormore “triggers” that are tied to or associated with a dispense. Asshown, upon the ACP 360 determining that a dispense has been requestedby the user, the process passes from step 511 to step 512. Step 512, aswell as step 502, can be characterized as additive vessel interfaceprocessing or pod interface processing. In step 512, the apparatuscontroller 350 can perform any of the processing as described above withreference to step 502. That is, is appreciated that a scenario of a newvessel 400 being inserted may warrant same or similar processing as asituation in which a dispense has been requested by the user. Inaddition to such processing, the apparatus controller 350 can alsoperform dispense processing as illustrated by step 513 of FIG. 25, i.e.in response to a request from the user to perform a dispense. Details ofsuch processing of step 513 are described below with reference to FIG.35 and the processing of subroutine 710. As in step 502, the processingof step 512 is not limited or constrained by the particular orderillustrated. The various processing of step 512 can be performed inparallel fashion and/or in serial fashion as may be desired and in theorder as desired. Such particulars of order can be based onpredetermined settings and/or configurations of the apparatus controller350.

FIG. 26 is a flowchart showing in further detail the apparatuscontroller 350 performs RFID “warnings” processing step 520, as calledupon from FIG. 25, according to principles of the disclosure. Theprocessing of step 520 relates to a situation where data has beencollected by the apparatus controller 350 relating to intake or dietaryconstraints of the user of the beverage apparatus 300. Such data may becharacterized collectively as “profile warnings data” that can be storedin record 4 in the vessel_1 database 377 (FIG. 19b ). For example, theprofile warnings data might include data indicating that the user isallergic to peanuts. Accordingly, the processing of the disclosureprovides for data in the vessel_1 database 377 to be compared with datain the tag memory portion (TMP) 430. More specifically, profile warningsdata 381-4 in the vessel_1 database 377 can be compared to “tag warningsdata” 431-13 that is stored in record 13 of the TMP 430. As reflected at520′, in FIG. 26, profile warnings data 381-4 from the vessel_1 database377 can be in the form of data records and/or data that has beengenerated by the ACP 360 to be compared to the tag warnings data. Forexample, the profile warnings data 381-4 stored in the data record 4 (inthe vessel_1 database 377) can be input through the beverage apparatus300 interface 310 from the user. Also, the profile warnings data 381-4in the vessel_1 database 377 can be downloaded from the server 20 orother data source. Other methodologies and/or data sources can beutilized so as to populate the profile warnings data 381-4 in thevessel_1 database 377.

As shown in FIG. 26, the process starts in step 520 and passes to step521. In step 521, the ACP 360 retrieves tag warnings data 431-13 fromthe tag 410 on the vessel or pod 400. For example, the tag warnings datamay include suitable indicia so as to represent attributes of theparticular additive that is stored in the vessel 400. For example, asreflected at 521″, the tag warnings data include “peanut”. It should beappreciated that such is a simplified example and that data utilized torepresent such information can be more complex in form and/orrepresentation. The tag warnings data can be retrieved from tag warningsdata 431-13.

Specific methodologies and processes can be utilized so as to exchangedata between the apparatus controller 350 and the tag 410. As reflectedat 521′, in FIG. 26, subroutines 530 and/or 560 can be invoked so as to(1) output a communication from the apparatus controller 350 to the tag410, and (2) input a communication from the tag 410 to the apparatuscontroller 350. Further details of such processing or described belowwith reference to FIG. 27 and FIG. 28.

After the tag warnings data 431-13 is retrieved from the tag 410 in step521, the processing passes on to step 522. In step 522, the ACP 360retrieves profile warnings data 381-4 from the vessel_1 database 377. Asreflected at 522′, for example, the tag warnings data 431-13 may includethe data “peanut”. After step 522, the processing passes to step 523.

In step 523, the ACP 360 performs comparison processing and determinesif there is a match between the profile warnings data 381-4 and the tagwarnings data 431-13. In performing such comparison, various processingcan be utilized so as to compare the various data in the tag warningsdata 431-13 with the profile warnings data 381-4 so as to determine ifthere are any matches. For example, based on the content (of theadditive) in the vessel 400, the tag warnings data 431-13 may containthe data: “peanuts” and “whey”. Such indicia reflects contents of thevessel 400. Such data will be compared with the profile warnings data381-4.

If the processor determines that there is a match in step 523, theprocess passes from step 523 to step 525. In step 525, the ACP 360outputs a communication to the TMP 430 to reflect that the particularvessel 400 should be disabled. Specifically, the ACP 360 writes to thevessel enabled data record 24 in the TMP 430. For example, the datawritten to the data record 24 could be “no” so as to toggle theparticular vessel 400 from an enabled disposition to a disableddisposition. Data can also be stored in the beverage apparatus 300 so asto reflect that the particular vessel 400 has been disabled. After step525, the process passes to step 526.

In step 526, the ACP 360 maps the “match” that was identified into anappropriate message to the user. For example, the ACP 360 outputs the“mapped to” message to the user interface of the beverage apparatus 300and/or outputs the message to a user device, such as a cell phone.

Then, the process passes to step 527 of FIG. 26. In step 527, processingpasses back to FIG. 25 and specifically passes back to step 502.

On the other hand, the ACP 360 may have not identified a match in step523, i.e. “no” in step 523. Accordingly, the process passes from step523 to step 524. In step 524, the ACP 360 outputs a communication to theTMP 430 so as to reflect that the particular vessel 400 should beenabled or should continue to be enabled. Specifically, the ACP 360writes to the vessel enabled data record 24 in the TMP 430. For example,the data written to the data record 24 could be “yes” so as to toggle ormaintain the particular vessel 400 in an enabled disposition.Alternatively, the ACP 360 can simply not write data to the data record24, in the TMP 430, so as to simply maintain the vessel 400 in anenabled disposition. Data can also be stored in the beverage apparatus300 so as to reflect the particular vessel 400 is indeed enabled.Accordingly, as reflected at 524′, if the processing of FIG. 26 wastriggered by a dispense request, that the requested dispense cancontinue, i.e. as requested by the user.

Then, process passes to step 527 as shown in FIG. 26. As describedabove, in step 527, processing passes back to FIG. 25 and specificallyto back step 502.

In the processing of FIG. 26, it should be appreciated that the ACP 360can provide for different levels of warning. For example, data in theprofile warnings data 381-4 might reflect that the particular user doesnot like “peanuts” (or prefers not to intake peanuts) but notnecessarily that the particular user is allergic to peanuts.Accordingly, if “peanuts” indicia is identified in the tag warnings data431-13 associated with a particular vessel 400, then the ACP 360 mightnot disable the particular vessel 400, but might rather just send acommunication to the user so as to warn or convey to the user theparticular content of the vessel 400. Other levels, degrees, or variancein warnings can be provided. Additionally, the inclusion of a particularingredient in a vessel 400 can be processed by the ACP 360 so as tolimit the intake of such ingredient by the user, i.e. as opposed toprecluding the intake of such ingredient by the user.

FIG. 27 is a flowchart showing processing associated with output of datafrom the apparatus controller 350 to the TMP 430, according toprinciples of the disclosure. More specifically, the processing of FIG.27 can be invoked or enabled in conjunction with the ACP 360 identifyinga requested output of data from the ACP 360 to the TMP 430. Processingof FIG. 27 can include subroutine 530 and subroutine 540. In thesubroutine 530, the ACP 360 performs “ACP to TPP” data transmissionprocessing. That is, processing is performed to transfer data from theapparatus controller 350 to the tag processing portion 420. In thesubroutine 540, the tag processing portion 420 performs “ACP to TPP”data transmission processing—from the processing perspective of the tagprocessing portion 420. As shown in FIG. 27, the process starts in step531. In step 531, the 560 performs decisioning so as to determine ifthere is data to output to the tag or RFID tag 410. For example, a queuecan be utilized in the apparatus controller 350. Upon the ACP 360identifying that there is data in the particular queue, processing canbe initiated so as to output or push out such data to the tag 410.Accordingly, if a yes determination is identified in the processing ofstep 531, processing passes to step 532.

In step 532, the ACP 360 encrypts the data to be output from theapparatus controller 350 to the TMP 430 in the tag 410. Additionally,the ACP 360 can associate a hashtag with the data. The tag 410 can havebeen previously provided with the hashtag. As reflected at 532′, the ACP360 then controls the transmission of data from the apparatus controller350 to the tag 410.

FIG. 27 also shows the processing performed by the tag 410, i.e., uponinput of the data that has been transmitted from the apparatuscontroller 350. In step 541, the tag processing portion 420 (TPP) inputsthe encrypted data along with the hash value. Then, the process passesto step 542. In step 542, the tag processing portion 420 applies a hashfunction (that can be stored in record 20 in the TMP 430) to the hashvalue that was input by the tag processing portion 420. Accordingly, thetag processing portion 420 converts the hash value to a hash functionoutput. Then, the process passes to step 543.

In step 543, the tag processing portion 420 compares the hash functionoutput to the expected output stored in the TMP 430. For example, theexpected output can be stored in the data record 21 in the TMP 430. Thetag processing portion 420 confirms a “match”—indicating that thereceived data is indeed appropriately from beverage apparatus 300. Ifthe tag processing portion 420 identifies that there is not a match,then the data, which was input, is ignored. Then, the process passesfrom step 543 to step 544.

In step 544, the tag processing portion 420 decrypts the data that wasinput from the apparatus controller 350. Then, the processing passes tostep 545. In step 545, the tag processing portion 420 stores the nowdecrypted input data and/or performs predetermined processing upon theinput data. For example, such predetermined processing could include thetag processing portion 420 placing the received data in predeterminedtag data records 431 in the tag 410.

FIG. 28 is a flowchart showing processing associated with output of datafrom the TMP 430 to the apparatus controller 350, i.e. from the tag tothe beverage apparatus 300, according to principles of the disclosure.The processing of FIG. 28 can be invoked or enabled in conjunction withthe tag processing portion 420 identifying a requested output of datafrom the tag 410 to the apparatus controller 350.

The processing of FIG. 28 can include subroutine 550 and subroutine 560.In the subroutine 550, the tag processing portion 420 performs “TPP toACP” data transmission processing. That is, processing is performed, bythe tag 410, to transfer data from the TMP 430 to the apparatuscontroller 350. In the subroutine 560, the ACP 360 performs “TPP to ACP”data transmission processing. Such processing is performed by theapparatus controller 350 upon receipt of data from the tag 410. As shownin FIG. 28, the process starts in step 551. In step 551, the tagprocessing portion 420 performs decisioning so as to determine if thereis data to output from the tag 410 to the apparatus controller 350. Forexample, a queue can be utilized in the tag 410. Upon the tag processingportion 420 identifying that there is data in the particular queue, theprocessing can be initiated so as to output or push out such data fromthe tag 410 to the apparatus controller 350. Accordingly, if a “yes”determination is identified in the processing of step 551, processingpasses to step 552.

In step 552, the tag processing portion 420 encrypts the data to beoutput from the tag 410 to the apparatus controller 350. Additionally,the tag processing portion 420 can associate a hashtag with the data.The apparatus controller 350 can have been previously provided with thehashtag. As reflected at 552′, the tag processing portion 420 controlsthe transmission of data from the tag 410 to the apparatus controller350.

FIG. 28 also shows the processing performed by the apparatus controller350, i.e. upon input of the data, which has been transmitted from thetag 410 to the apparatus controller 350.

In step 561, the ACP 360 inputs the encrypted data along with the hashvalue. In step 562, the ACP 360 applies a hash function (that can bestored in record 5 in the vessel_1 database 377) to the hash value thatwas input by the ACP 360. Accordingly, the ACP 360 converts the inputhash value to a hash function output. Then, the process passes to step563. In step 563, the ACP 360 compares the hash function output to theexpected output stored in the controller. For example, the expectedoutput can be stored in the data record 6 in the vessel_1 database 377.The ACP 360 confirms a “match”—indicating that the received data isindeed appropriately from the tag 410 as expected. If the ACP 360determines that there is not a match, then the data, which was input, isignored. Then, the process passes from step 563 to step 564.

In step 564, the ACP 360 decrypts the data that was input from the tag410. Then, processing passes to step 565. In step 565, the ACP 360stores the now decrypted data, which was input, and/or performspredetermined processing upon the input data. For example, suchpredetermined processing could include the ACP 360 placing the receiveddata in predetermined memory destinations in the apparatus databaseportion 370.

FIG. 29 is a flowchart showing details of user preference processing,according to principles of the disclosure. Specifically, FIG. 29 showsdetails of the “ACP 360 performs warnings user preference processing”step 570, in accordance with at least one embodiment of the disclosure.For example, the processing of step 570 can be called in response to auser selection of a menu item, in a GUI. The GUI might be presented tothe user via the interface 310 or a user device associated with thebeverage apparatus 300. The process starts in step 570, and passes tostep 571. In step 571, the ACP 360 determines if “warnings” userpreference processing has been initiated. If yes in step 571, theprocess passes to step 572. In step 572, the ACP 360 interfaces with theuser to initiate such “warnings” user preference processing. Then, theprocess passes to step 573.

In step 573, the ACP 360 performs engagement processing with the user toinput allergies, drug constraints, dietary preferences, and relateddata. For example, such interface can be in the form of a sequence ofquestions presented to the user via a GUI. To perform such processing,the ACP 360 calls subroutine 580. Details of such subroutine 580 are setforth in FIG. 30 and described below. After the processing of step 573,the process passes to step 574.

In step 574, ACP 360 saves data generated in processing of step 573 tothe apparatus database portion 370. Then, the process passes to step575. In step 575, the processing terminates.

Further details with the processing of subroutine 580 are described withreference to FIG. 30. In FIG. 30, the ACP 360 interfaces with the userto pose a first question which might be characterized as “question #1.The question can relate to allergies, drug constraints, dietarypreferences, and/or other dietary or intake considerations orpreferences (that can collectively be characterized as “intake data”)that the user wants to input into (and be known by) the beverageapparatus 300. As reflected in step 581, of FIG. 30, the processing caninclude generation of a question or use of other inquiry technique,input of response from the user, and population of the user profilebased on the response. The user profile can be stored in the apparatusdatabase portion 370.

As shown in FIG. 30, steps 581, 582, 583 represent that numerousquestions can be presented to the user so as to input the desired intakedata. Such questions can be presented in hierarchical manner so as to“drill down” into areas that are identified (by the user) as relevant tothe user—in conjunction with quickly eliminating areas that are not ofrelevance to the particular user. Further details of the processing ofthe third question, in FIG. 30, is illustrated. As reflected at 583A′ inFIG. 30, the apparatus database portion 370 can include one or more datarecords that associate a particular question with a “flag” term or code,i.e. indicia. For example, the question might be: “Are you allergic topeanut based foods?” and the flag term might be the indicia “peanuts”.Such question can be presented to the user in step 583A. Then, theprocessing passes to step 583B. In step 5803B, the ACP 360 determines ifinput from the user was “yes”. If the determination in the processing ofstep 583B is “no” then the process passes to step 583D.

In step 583D, the ACP 360 terminates processing for the particularquestion. Then, in step 583F, processing advances to the next question.Such next question might be question #4 as reflected in step 584 of FIG.30. After step 584, the process passes to step 586. In step 586, theprocess passes back to FIG. 27.

On the other hand, the decision processing of step 583B may determine“yes”. Accordingly, the processing passes from step 583B to step 583C.In step 583C, the ACP 360 populates the user profile to include the flagterm “peanut”. The ACP 360 than terminates processing for the particularquestion. Then, as described above, the processing passes to step 583F.In step 583F, the ACP 360 interfaces with the user to present the nextquestion. Accordingly, as reflected in FIG. 30, the user profile can bepopulated with specific, predetermined terms that reflect “intake data”that is associated with the user. Such intake data can be standardizedwith corresponding intake data that is stored on the TMP 430 of the tag410. Accordingly, such processing allows the ACP 360 to determine ifthere is a match between the profile warnings data 381-4 (in theapparatus database portion 370) and the tag warnings data 431-13 (in theTMP 430). If a match is determined, suitable processing can beperformed. Such suitable processing can include the disabling and/orconstraining of dispense of the additive in the particular vessel 400.

FIG. 31 is a flowchart showing in further detail the ACP 360 performs“expiry” processing step 600, as called on from FIG. 25, in accordancewith the principles of the disclosure. As shown, the processing startsin step 600 and passes to step 601. In step 601, the ACP 360 readsparticular data from the tag memory portion (TMP) 430. Specifically, theACP 360 reads the fill timestamp data from the tag data record 5 (of theTMP 430) and an expiry period from the tag data record 14 (of the TMP430). In FIG. 24, such data is illustratively shown in the TMP 430,which is disposed on the RFID tag 410, which is a part of or attachedonto the pod or vessel 400. It is appreciated that the organization,architecture, and specific positioning of data in the TMP 430 (FIG. 24)can be varied as desired. As reflected at 601′ (FIG. 31), thesubroutines 530 and/or 560 can be invoked so as to output data (from theapparatus controller 350) to the tag 410 and to input data from the tag410.

After step 601, processing passes from step 601 to step 602. In step602, the ACP 360 determines the expiry time. Specifically, the ACP 360adds the fill timestamp on to the expiry period, so as to yield theexpiry time. For example, a fill date of Oct. 1, 2019 plus an expiryperiod of 2 months would yield a expiry_time of Dec. 1, 2019. In someembodiments of the disclosure, the tag data record can include anexpiration date, i.e. rather than calculating the expiration date asdetermined in step 602.

In step 603, the ACP 360 determines if the expiry time has not beenattained, i.e. is the current date/time less than the expiry date/time.If no in step 603, the processing passes to step 605. In step 605, theACP 360 outputs a communication to the user that the particular pod,i.e. vessel, has expired and cannot be used. Then, in step 606, the ACP360 outputs a communication to the tag so as to overwrite record 24 inthe TMP 430 so as to represent that the vessel is disabled. As a result,the particular vessel will be disabled. It should be appreciated that inprocessing in response to a dispense request, the ACP 360 can interfacewith the tag 410 so as to determine whether or not the particular vessel400 is enabled. If the vessel is not enabled, i.e. as in the processingof step 606 in FIG. 31, then the dispense request will not be completedby the ACP 360.

In other embodiments, in the situation that the vessel has expired, theACP 360 may not disable the particular pod or vessel 400. Rather, theACP 360 may just send a communication to the user indicating that thepod 400 has expired. After step 606, of FIG. 31, the process passes tostep 607. In step 607, the processing routine is terminated.

On the other hand, in step 603, the ACP 360 may determine that theexpiry time has not been attained. Accordingly, the decisioning in step603 yields a “yes” determination. As a result, the process passes tostep 604. In step 604, the ACP 360 writes to the TMP 430 to set the podenabled variable (in the data record 24 in the TMP 430) to “yes”. Inother embodiments, the ACP 360 may not write new data to the TMP 430,but rather may simply leave the tag data record 24, in the TMP 430, inthe enabled state.

In accordance with at least some embodiments of the disclosure,expiration or expiry related processing can be varied from theprocessing as shown in steps 601, 602 and 603 of FIG. 31. In anembodiment, there can be multiple stages of expiration or shelf life ofa pod/additive vessel. There can be one expiration date by which a pod,i.e. contents of a pod, should be used subsequent to production of thepod. Such first expiration date might be described as a “best-byexpiration date”. A second expiration date can be initiated by initialuse of a pod/additive vessel. Such might be described as a “staleexpiration date”—in that content of the pod 250 may go stale after acertain time period, e.g. 21 days, of being “opened”. To explain, a podor vessel 250 as shown in FIG. 5B can include a vessel cap or cap 248.The cap 248 can be positioned over the piston head 253 and port 255. Thecap 248 can be secured onto the end of the pod via threads, snaps orother arrangement. The cap 248 can including a sealing surface 249and/or other structure that seals the pod 250, which contains additiveor concentrate. The cap 248 can prevent evaporation of additive in thepod 250. The cap 248 can prevent contaminates from entering the pod 250and maintain additive, in the pod, in an isolated state from the ambientenvironment. The pod 400, as shown in FIG. 17 for example, can include asame or similar cap to cover the piston head 405 and one-way valve 407.In use, a user can remove the cap 248, with reference to FIG. 5B, beforeinserting the pod 250 into a receptacle of the beverage apparatus 200.Such removal of the cap 248 can be equated to “opening” of the pod. Oncethe cap 248 is removed, the second expiration date can start to run oraccrue. For example, the second expiration date (i.e. the “staleexpiration date”) can run for 21 days from when the pod 250 is firstinserted into the receptacle of the beverage apparatus and theparticular pod is detected by a processor of the beverage apparatus.Insertion of the pod into the beverage apparatus is indicative that thecap 248 has been removed, i.e. that the pod has been opened. Thebest-by_expiration_date might be 2 months from production date. Theexpiration dates may vary based on the particular additive.

To further explain, alternative processing 600′ can be performed asillustrated by process steps 601′ and 603′ of FIG. 31. Step 601′ can beperformed in lieu of step 601, and step 603′ can be performed in lieu ofstep 603. In step 601′ the ACP reads the best-by_expiration_date and thestale_expiration_date from the RFID tag. For example, thebest-by_expiration_date can be written to the RFID tag in production andthe stale_expiration_date can be written to the tag by the beverageapparatus upon insertion of the RFID tag into the beverage apparatus.Then, in step 603′, the ACP determines if (Iscurrent_date<best_by_expiration_date) AND (Iscurrent_date<stale_expiration_date)). In such illustrative logic, it canbe understood that a later date possesses a greater value. If yes instep 603′, then processing can proceed to step 604 and the pod isenabled. If no in step 603′, then the process passes to step 605 and thepod is not enabled. Other options can be provided. For example, eventhough the best-by_expiration_date and/or the stale_expiration_date havebeen attained—the pod can still be enabled, but a suitable communicationcan be output to the user. The suitable communication can advise theuser of the disposition of the pod.

FIG. 32 is a flowchart showing details of the “ACP 360 performs productinformation processing” step 610 that is called from FIG. 25, accordingto principles of the disclosure. The processing FIG. 32 relates toinputting information, into the beverage apparatus 300, from the tag410, and displaying such information as well as performing othermanipulation of such information. For example, product information canbe retrieved from tag 410 and displayed either on the beverage apparatus300 and/or on a user device, for example. As shown in FIG. 32, theprocess starts in step 610 passes to step 611.

In step 611, the ACP 360 determines if settings and/or operational modedictates to display product information regarding the pods or vessels400 that are in use. If yes, then the process passes from step 611 tostep 612. In step 612, the ACP 360 determines the particular productinformation that is dictated (by the settings and/or operational mode,for example) that should be displayed. Additionally, the ACP 360 candetermine the particular channel upon which to display such information.For example, as reflected at 612′, the ACP 360 determines that productname is the product information to be displayed on the user device orbeverage apparatus 300. The processing passes from step 612 to step 613.In step 613, the ACP 360 outputs a request to the tag processing portion420 to retrieve the requested information, product name, from the tagprocessing portion 420. As reflected at 613′, subroutine 530 can beinvoked so as to output such request to the tag processing portion 420.The request from the ACP 360 can instruct the tag processing portion 420to access data in data record 3 in the TMP 430, as shown in FIG. 24.Such data in the data record 3 can simply include the product name.Alternatively, such data in the data record 3 can include a code that isutilized by the ACP 360 so as to “look up” the name of the product. Forexample, such lookup data may be downloaded by the beverage apparatus300 from the ecosystem server 20.

After step 613, the processing passes to step 614. In step 614, the ACP360 inputs requested information, i.e. the product name, from the tagprocessing portion 420. As reflected at 614′ in FIG. 32, subroutine 560can be invoked as described above. After step 614, the process passes tostep 615.

In step 615, the ACP 360 outputs the data (product name) to the userdevice for display on the user device. For example, the user devicemight be a cell phone 106. Additionally, the ACP 360 can output thedata, for display, to the interface 310 for display.

After step 615, the processing passes to step 616. In step 616, theprocessing routine is completed and is terminated. FIG. 33 is aflowchart showing details of the “ACP 360 performs apparatus colorprocessing” step 620 is called from FIG. 25. The processing of FIG. 33relates to a situation in which data is pulled from the TMP 430 so as tocontrol color display provided in or on the beverage apparatus 300. Forexample, the dispense of a particular vessel or pod 400 can beaccompanied by the display of a particular color. For example, thedisplay of the particular color can be provided by a colored LED in thebeverage apparatus 300. The LED can be provided in the internal volumeor chamber 316 in the beverage chamber housing 315. As shown in FIG. 33,the process starts in step 620 and passes to step 621.

In step 621, the ACP 360 determines if a dispense is to be performed andthat settings and/or operational mode dictate to display light inconjunction with the dispense. If no, then the processing passes fromstep 621 to step 625. In step 625, the processing routine is completedand is terminated. On the other hand, the decisioning of step 621 maydetermine that the “if” statement of 621 is true. Accordingly,processing passes from step 621 to step 622.

In step 622, the ACP 360 outputs a request to the tag processing portion420 to retrieve the requested information regarding color from TMP 430.For example, as reflected at 622′, subroutine 530 can be invoked. Therequest from the ACP 360 can include particulars so as to dictate (tothe tag processing portion 420) to retrieve color data from tag datarecord 15 in the TMP 430. The RGB color scheme is used herein forillustrative purposes. However, it should be appreciated that othercolor schemes and/or other color values can be utilized in the practiceof the disclosure. After step 622, process passes to step 623.

In step 623, the ACP 360 inputs the requested information (the RGB_pod1)data from the TMP 430. As reflected at 623′ of FIG. 33, subroutine 560can be invoked as described above. After step 623, the processing passesto step 624. In step 624, the ACP 360 enables apparatus color (light)processing during dispense—so that light will be generated duringdispense from the pod or vessel 400. Data regarding when and how toprovide particular light or illumination to the beverage apparatus 300can be included in the tag data record 15 in the TMP 430. For example,such data may dictate for the beverage apparatus 300 to provideillumination in other dispensing scenarios of the beverage apparatus300. For example, an LED unit or assembly can be provided, in the bottle300, that includes different colored bulbs, such as a red, green andblue bulb. The different colored bulbs can be selectively lit or notlit. The data record 15 can include data based on which the bottlecontrols which bulbs to light or not light. Accordingly, the emittedcolor can be controlled.

After step 624, the processing passes to step 625. In step 625, theprocessing routine is completed and is thus terminated.

FIG. 34 is a flowchart showing in further detail the ACP 360 “performsproduct recall processing” step 630 as called from FIG. 25, according toprinciples of the disclosure. Such processing relates to theidentification of a recalled vessel 400 that is inserted into thebeverage apparatus 300. However, the processing of FIG. 34 can also beapplied to other attributes and/or characteristics of a vessel in thebeverage apparatus 300.

As shown, the process starts in step 630 and passes to step 631. In step631, the ACP 360 reads attribute information from the TMP 430. Inparticular, the ACP 360 can read the facility ID data in tag data record8 of the TMP 430. The ACP 360 can read the lot number data in tag datarecord 7 in the TMP 430. Then, the process passes to step 631.

In step 631, the ACP 360 retrieves product recall data from a server orother backend system. For example, the ACP 360 can retrieve the productrecall data from the ecosystem server 20 as shown in FIG. 17. This datais then stored in the apparatus database portion 370. Such productrecall data might be represented by a facility identification (ID)and/or lot number identification. Other tracking data can be used so asto identify a recalled vessel or group of vessels. Then, the processpasses to step 633.

In step 633, the ACP 360 determines if there is a match between datainput from the TMP 430 of the vessel 400 vis-à-vis the data input instep 631. If there is not a match, then the processing passes to step634. In step 634, the ACP 360 writes to the TMP 430 to enable theparticular vessel. Specifically, the ACP 360 writes to the data record24 so as to enable the particular vessel 400. Then, processing passes tostep 637. In step 637, processing routine is terminated.

On the other hand, it may be determined in step 633 that there wasindeed a match between data retrieved from the vessel 400 vis-à-vis datainput from the ecosystem server 20 in step 631. Accordingly, if yes instep 633, the process passes from step 633 to step 635.

In step 635, the ACP 360 interfaces with the user to advise the userthat the vessel or pod 400 is subject to a recall and is not usableand/or is subject to some other restriction or constraint. As reflectedat 635′, processing can also include communicating further informationto the user regarding the recalled pod. For example, such informationmight include logistics in securing replacement parts or replacement forthe recalled pod.

After step 635, the process passes to step 636. In step 636, the ACP 360writes to the pod database so as to disable the particular pod or vessel400. For example, the ACP 360 writes “no” to the data record 24 in theTMP 430. As reflected in 336′ in FIG. 34, subroutine 530 can be invokedin such writing of data to the TMP 430. After step 636, the processingpasses to step 637. In step 637, processing routine is terminated.

The process shown in FIG. 34 can be applied to other scenarios orcircumstances other than a recall scenario. The process can be appliedin any of a wide variety of situations in which identifying data can bestored on the TMP 430 and matched with data stored on the beverageapparatus 300, input from the ecosystem server 20, input from some otherthird party, and/or input from some other resource. The matching of dataand/or a determination that the data does not match can be utilized todetermine the state of the particular vessel 400, particular processingthat should be applied to the particular vessel 400, particularcommunications that should be output to the user in conjunction with useof the particular vessel 400 and/or other processing. In general, thebeverage apparatus 300 can input and write data to the tag 410 so as todetermine state of a particular vessel 400, particular processing thatshould be applied to the particular vessel 400, particularcommunications that should be output to the user in conjunction with useof the particular vessel 400 and/or other processing.

FIG. 35 is a flowchart showing details of the ACP 360 “performs dispenseor dispensing processing” step or subroutine 710 as called from in theprocessing of FIG. 25, according to principles of the disclosure. Theprocessing of FIG. 35 relates to a situation where a dispense isrequested by the user and various processing is performed in conjunctionwith such requested dispense. As shown, the process starts in step 710and passes to step 711. In step 711, the ACP 360 performs “warningprocessing”. In such processing, subroutine 520 of FIG. 26 can be calledupon by the ACP 360. After step 711, the process passes to step 712.

In step 712, the ACP 360 determines if a dispense has been requested bythe user. The ACP 360 also determines that the pod or vessel 400 isenabled. If a yes determination is determined in step 712, the processpasses to step 713. In step 713, the ACP 360 determines if a tastepreference feature is enabled. As described below, such taste preferencefeature allows a user to vary a default or predetermined dose amountstored in the pod 400.

If no in step 713, taste preference feature is not enabled, theprocessing passes to step 715. In step 715, ACP 360 retrieves defaultdose data, i.e. dispense volume data, from the tag regarding how muchadditive is to be dispensed. For example, such data can be the number ofmilliliters to be dispensed. Such data can be stored in data record 10in the TMP 430. After step 715, the processing passes to step 716.

On the other hand, it may be determined that a taste preference featurehas been enabled, i.e. yes in step 713. Accordingly, the processingpasses from step 713 to step 714. In step 714, the ACP 360 performstaste preference processing. In particular, subroutine 730 of FIG. 36 iscalled upon or invoked. After such processing is performed in step 714,the processing passes to step 716. As reflected at 714′, in FIG. 35,subsequent to performing the subroutine 730 (step 714), a dispensevolume is in memory so as to be used for further processing as describedbelow. Accordingly, processing coming into step 716 has generated orretrieved a dispense amount. In step 716, the ACP 360 reads fill leveldata from a predetermined data field of the RFID tag 14. Such fill leveldata represents a specific state of the vessel 400 at a particular pointin time. As time advances and use of the vessel is incurred, such stateof the vessel 400 will vary over time. The processing of FIG. 35 isperformed to provide reactive or responsive processing, by the ACP 360,to address the change in state experienced by the vessel 400. The filllevel data that is read in step 716 can be stored in data record 23 inthe TMP 430, as shown in FIG. 24. After step 716, processing passes tostep 720.

In step 720, the processing determines if the dispense volume requestedby the user can be satisfied by the amount of additive remaining in thevessel 400. In other words, the processing determines if the dispensevolume is less than the fill level of the vessel 400. If yes, then theprocessing passes from step 720 to step 724. In step 724, the ACP 360controls the dispensing assembly to dispense the requested amount ofadditive from the pod into the liquid in the beverage apparatus 300.That is, such liquid in the beverage apparatus 300 is contained in theapparatus cavity, internal volume, or chamber 315 as described above. Asreflected at 723′ in FIG. 35, the dispense processing can includeapparatus color or light processing as illustrated in FIG. 33. Afterstep 724 as shown in FIG. 35, the processing passes to step 725.

In step 725, the ACP 360 generates updated fill level field to reflectthe dispense that just occurred. The updated value is written back tothe tag, i.e. so as to update the fill level data field. Such value canbe constituted by the ACP 360 decrementing fill level by the dispensevolume that has just been dispensed. Such updated value can be writtenover the previous value stored in data record 23 in the TMP 430.Accordingly, the ACP 360 updates the tag or RFID tag 410 so as toreflect the current status of the vessel 400.

After step 725, the process passes to step 726. In step 726, ACP 360outputs a communication to the user that the requested dispense has beenperformed. Then, in step 727, the ACP 360 stores data regarding thedispense event in the apparatus database portion 370. Then, theprocessing passes to step 728. In step 728, the processing routine isterminated.

On the other hand, it may be determined in step 720 that the fill levelis not greater than the dispense volume, i.e. no in step 720.Accordingly, the processing passes from step 720 to step 721. In step721, the ACP 360 outputs a communication to the user that the requesteddispense cannot be performed. The ACP 360 can provide details to theuser. Then, in step 722, ACP 360 stores data regarding the dispenseevent, or in such situation the attempted dispense event. Then theprocessing passes to step 723. In step 723, the processing routine isterminated.

FIG. 36 is a flowchart showing in further detail the ACP 360 performstaste preference processing as called upon from FIG. 35, according toprinciples of the disclosure. As shown, the process starts in step 730and passes to step 731. In step 731, the ACP 360 determines if there isa “taste preference coefficient” (TPC) in memory. As described below,the TPC can be utilized so as to vary a standard or default dose valuestored in the TMP 430.

If no in step 731, then the process passes to step 732. In step 732, ACP360 interfaces with the user to input a new or updated TPC value. Then,the processing passes to step 733.

On the other hand, a determination may be made, by the ACP 360 in step731, that a TPC is indeed in memory. Accordingly, a yes determination isdetermined in step 731. Accordingly, the process passes from step 731 tostep 733. As reflected at 731′ of FIG. 36, a user setting can beutilized to dictate other order processing or processing. For example, auser may be provided functionality to interface with the system uponeach dispense so as to adjust the dispense amount. Other variations canbe provided. Also, a setting can be provided to the user such that tastepreference processing may not be enabled.

With further reference to FIG. 36, in step 733, the ACP 360 retrievesdispense volume data, which may be retrieved in the form of a defaultdose from the tag data record 10 of the TMP 430. Such dispense volumedictates how much additive has been requested to be dispensed. Then, theprocess passes from step 733 to step 734.

In step 734, the ACP 360 adjusts the dispense volume based on the TPC togenerate a modified dispense volume. In accordance with at least oneembodiment of the disclosure, the dispense volume can be multiplied bythe TPC so as to generate a modified dispense volume. Such modificationof the dispense volume can increase the dispense volume or decrease thedispense volume based on the value of the TPC. Other adjustmentmechanism can be used. After step 734, the processing passes to step750.

In step 750, the ACP 360 determines if the modified value is less thanthe maximum dose of the additive. Such maximum dose of the additive canbe retrieved by the ACP 360 from the data record 12 in the TMP 430. Suchmaximum dose can be based on a variety of considerations includingdietary considerations.

It may be determined in step 750 that the modified value is not lessthan the maximum dose. Accordingly, the modified dose exceeds themaximum dose. Accordingly, a no determination is determined in step 750.As a result, the processing passes from step 750 to step 751. In step751, the ACP 360 interfaces with the user to advise the user of thesituation and to input acknowledgment of the situation from the user.For example, the processing requests the user to click “OK”. Then, theprocess passes from step 751 back to step 732. In step 732, the ACP 360interfaces with the user to input a new or updated TPC value.

On the other hand, a yes determination may be determined in step 750.Accordingly, the processing passes from step 750 to step 752. In step752, the ACP 360 determines if the modified value is more than a minimumdose of the additive. Such minimum dose of the additive can be retrievedfrom the data record 11 in the TMP 430, in the tag 410 of the vessel400.

If no in step 753, then the ACP 360 interfaces with the user to advisethe user that the modified dose is below the lower limit for theadditive. Processing is then performed to request acknowledgement fromthe user, in step 753. On the other hand, a yes determination may berendered in step 752. Accordingly, the process passes from step 752 tostep 754. In step 754, the ACP 360 forms processing to confirm that anyother applicable thresholds or constraints are satisfied by the dispenserequested. For example, capacity constraints of the internal volume orchamber 315 can be taken into account. Then, in step 755, a value of thedispense volume is assigned (or “gets”) the modified dispense volume.Then, the process passes to step 756. In step 756, the processing passesback to FIG. 35 in step 716. Processing then continues as describedabove.

The processing in accordance with the principles of the disclosure allowa physical state of the beverage apparatus 300 and/or a vessel 400,which is disposed in the beverage apparatus 300, to be monitored.Additionally, operation of the beverage apparatus can be performed so asto control a physical state of the vessel 400. Operation of the beverageapparatus can be performed so as to attain a desired physical state ofthe vessel 400. In such functionality, data can be retrieved from thetag 410 (affixed to the vessel 400) and data can be written to the tag410. Additionally, a state or event experienced by the beverageapparatus 300 and/or the vessel 400 can be written to the tag 410. Forexample, such event might be the sudden acceleration or deceleration ofthe beverage apparatus 300, such as from a drop. Such data can bewritten to the tag 410, represented in data form, so as to controlfuture operations of the beverage apparatus 300 relative to theparticular vessel 400.

As described above and shown in FIG. 18, the beverage apparatus 300 caninclude a vessel 400. The vessel 400 can include a tag 410. The tag 410can be an RFID tag. The tag 410 can be in communication with thetransceiver 341 (of the beverage apparatus) via an antenna 342. Thetransceiver 341 can be in communication with the controller 350. Asdescribed above with reference to FIG. 23, the RFID tag 410 can includea tag processing portion (TPP) 420 and a tag memory portion (TMP) 430.

Hereinafter, further features will be described relating to tags or RFIDtags of the beverage apparatus and related structure and processing, inaccordance with the present disclosure. FIG. 37 is a schematic diagramshowing a communication assembly 840 in accordance with at least oneembodiment. The communication assembly 840 can be provided in the bottle300 of FIG. 22 or in a similar bottle. The communication assembly 840can include a controller 350. The communication assembly 840 can be aseparate assembly vis-à-vis a main or central controller or othercontroller of the beverage apparatus. The communication assembly 840 canalso include a transceiver or RFID transceiver 841, as well as one ormore antennas 830. The antennas 830 can include a first antenna, secondantenna 830′ and a third antenna 830″. The antennas 830 can be ofsimilar structure.

As shown in FIG. 37, the transceiver 841 can be connected to theantennas 830 via an antenna switch 900. More specifically, thecontroller 350 can be in communication with the antenna switch 900 via acable or control cable 844. The cable 844 can provide communicationbetween the controller 350 and the antenna switch 900 and provide powerto the antenna switch 900. The cable 844 can be part of thecommunication pathway 357 described above.

A cable 842 can provide communication between the controller 350 and thetransceiver 841, as well as providing power to the transceiver 841. Acable 843 can provide communication between the transceiver 841 and theantenna switch 900. The cable 843 can also provide power to the antennaswitch 900. The various cables, wires, or other communication pathwaysof FIG. 37 can be included in or part of a communication pathway 357 ofthe beverage apparatus 300.

The antenna switch 900 can be connected to each of the three antennas830. The three antennas 830 can be used to communicate, respectively,with the three vessels disposed in respective receptacles of thebeverage apparatus, such as receptacles 390 described above. The antennaswitch 900 can be connected to the antenna 830 via an antenna connectioncable 834. The antenna switch 900 can be connected to the second antenna830′ via a second connection cable 834′. The antenna switch 900 can beconnected to the third antenna 830″ via a third connection cable 834″.In accordance with principles of the disclosure, the antenna switch 900can control which antenna 830 is in communication with the transceiver841 via control of the antenna switch 900. Details of the manner inwhich the antenna switch 900 is controlled and the manner in which theantenna switch 900 controls connection between the antennas 830 and thetransceiver 841 are described below.

In an alternative embodiment, the transceiver 841 can be physically indata communication with each of the antennas (830, 803′, . . . )simultaneously. In such arrangement, only one of the antennas may be oris energized so as to communicate with a respective RFID tag (of a pod)through such energized antenna. The antenna(s) that are not energizedwill not afford communication to a respective RFID.

That is for example, in the alternative arrangement shown in FIG. 37A,antenna 830 can be powered, as controlled by the antenna switch 900′.Accordingly, only the powered antenna 830 will provide datacommunication between the transceiver 841 and a respective RFID tag (ofa pod). Then, when the controller needs to communicate with another pod(that is associated with antenna 830′), the antenna switch canpower-down the antenna 830 (by turning “off” switch 3711) and power-upthe antenna 830′ (by turning “on” switch 3712). Once powered up, theantenna 830′ will then communicate with its respective RFID/pod so as totransfer data between such further pod and the transceiver 841. Theantenna switch 900′ can be controlled by the controller 350. Thus, datacommunication lines/wires can be separate vis-à-vis power communicationlines/wires. For example, with reference to FIG. 37A, a data line fromthe transceiver 841 to the antenna 830 can be shared (or in a commoncommunication circuit) with a data line from the transceiver 841 to theantenna 830′. This can be possible since only the antenna that isenergized will convey data between such antenna's pod and thetransceiver 841. That is, the antenna that is not energized will nottransmit data, in accord with this embodiment.

Accordingly, in an arrangement, a first antenna 830 and a second antenna830′ can be in communication with a transceiver 841. The first antennacan be associated with a first power supply 3721. The second antenna canbe associated with a second power supply 3722. The antenna switch 900′,i.e. a selection portion, can be controlled, by the controller 350/ACP360, to selectively energize the antenna 830 with the first power supply3721 OR energize the antenna 830′ with the second power supply 3722. Asingle power supply or originating power supply or source 3700S can beused—and the antenna switch 900′ can control which antenna (830 or 830)is powered by the single power supply 3700S. The antenna (830, 830) thatis energized will provide data communication with its RFID, of apod—whereas the antenna(s) that is not energized will not provide datacommunication with its RFID/POD. FIG. 38 is a schematic diagram showingfurther details of the communication assembly 840 mounted on a supportplatform 808. For example, the support platform 808 might be constitutedby the bottom support platform 309 of the beverage apparatus 300. Thesupport platform 808 can be constructed of plastic, metal, or othersuitable material. The support platform 808 can be part of the structureof the beverage apparatus 300. The support platform 808 can include aplatform body 810. The platform body 810 can include an upper surface811, as illustrated in FIG. 38. Various components of the communicationassembly 840 can be mounted to the platform body 810, and specificallyto the upper surface 811 of the platform body 810. The controller 350,the transceiver 841, and the antenna switch 900 can be mounted to theupper surface 811. Various wires, cables, communication pathways, orother communication elements—including elements 842, 843, 844, 834—canbe mounted to or integrated into the platform body 810. As shown in FIG.38, the connection cable or antenna connection cable 834 can extendbetween the antenna switch 900 and the antenna 830.

The platform body 810 can include antenna cable holes 823, which caninclude a first antenna cable hole. The antenna cable holes 823 can alsoinclude a second antenna cable hole 823′ and a third antenna cable hole823″. The antenna cable holes 823 provide for passage, respectively, ofeach of the antenna connection cables 834, i.e. so as to extend from theupper surface 811 to each of the antennas 830. The construct of theantenna cable holes 823 can be varied depending on the particularconstruct of the antenna 830 within the platform body 810. For example,the antenna 830 might be provided on a lower surface 812 of the supportplatform 808. With such arrangement, the antenna cable holes 823 may bein the form of through apertures that extend through the platform body810. However, it may be the case that the antenna 830 is indeed embeddedinto the platform body 810. Accordingly, the antenna cable holes 823might be in the form of grooves or slots that extend to the antenna 830and that provide a pathway for the antenna connection cable 834.Further, in some embodiments, the antenna 830 might be disposed on theupper surface 811. In such arrangement, there may not be need for theantenna cable holes 823.

The platform body 810, and other platform bodies or structures of thebeverage apparatus, can include one or more receptacle apertures 820.The receptacle apertures 820 can include a first receptacle aperture.The receptacle apertures 820 can include a second receptacle aperture820′ and a third receptacle aperture 820″. The receptacle aperture 820can include an inner edge or wall 821. The second receptacle aperture820′ can include an inner edge or wall 821′. The third receptacleaperture 820″ can include an inner edge or wall 821″. The receptacleaperture can accommodate a receptacle to retain a pod in suchreceptacle.

The antenna 830 is shown schematically in FIG. 37, in accordance with atleast some embodiments of the disclosure. The antenna 830 can include aspiral configuration. In at least one embodiment, the spiralconfiguration can extend around all or a portion of the receptacleaperture 820. In other words, the antenna 830 can surround or encompassthe inner edge or wall 821 of the receptacle aperture 820. By thearrangement of the antenna 830 encircling the receptacle aperture 820,communication can be provided between the antenna 830 and an RFID tag410 (of a pod 400 that is disposed in the particular receptacle aperture820).

In accordance with the disclosure, the particular nature ofcommunication pathways 357 in the beverage apparatus 300 can be variedas desired. Accordingly, while a “cable” may be described as connectingvarious components, other communication pathways can be utilized asdesired. A cable as described herein can include one or more wiresand/or other construct so as to provide electrical power or datacommunication between two connected components. A communication pathwayas described herein can include one or more cables, wires and/or otherconstruct so as to provide electrical power or data communicationbetween two connected components.

FIG. 39 is a schematic diagram showing details of the communicationassembly 840 and support platform 808. In particular, FIG. 39 shows alower surface 812 of the support platform 808. In the embodiment of FIG.39, the antennas 830 are mounted on the lower surface 812 so as to bevisible. However, in other embodiments, the antennas 830 can be embeddedinto the platform body 810 so that the antennas 830 are not visible.FIG. 39 also shows that antenna connection cables 834 pass through theantenna cable holes 823. The antenna cable holes 823 can include antennacable holes 823′, 823″.

FIG. 40 is a schematic diagram illustrating further details of theantenna 830. As described above, the antenna 830 can wrap around orencircle the receptacle aperture 820. The antenna 830 can be constructedof multiple windings or loops. The antenna 830 can be connected to theantenna switch 900 via antenna connection cables 834. The antennaconnection cables 834 can include a first wire 834A and a second wire834B. Each of the first wire 834A and the second wire 834B can be inconnection with the antenna switch 900—so as to selectively provide forthe exchange of data between the antenna 830 and the transceiver 841,via the antenna switch 900. The antenna 830 can wrap around or encirclethe receptacle aperture 820 completely or some desired amount such as90% around, 80% around or some other amount as may be desired. Asdescribed above, the antenna switch 900 can control which antenna 830the transceiver 841 is connected to. In a first disposition of theantenna switch 900, the transceiver 841 may be connected to a firstantenna 830 and only two such first antenna 830. In a second dispositionof the antenna switch 900, the transceiver 841 may be connected only tothe second antenna 830′. In a third disposition of the antenna switch900, the transceiver 841 may be connected only to the third antenna830″.

FIG. 41 is a schematic diagram showing further details of thecommunication assembly 840, in accordance with at least some embodimentsof the disclosure. In particular, FIG. 41 shows details of an antennaswitch 900. The antenna switch 900 of FIG. 41 is a physical switch. Suchphysical switch has moving parts so as to control which antenna 830 isconnected to the transceiver 841. In other embodiments, as describedbelow other technology can be utilized so as to control which antenna830 is connected to the transceiver 841.

As shown in FIG. 41, the antenna switch 900 can include what can bedescribed as a moving board 910. The moving board 910 can be controlledby an actuator 930. The actuator 930 can include an actuator body 931.The actuator 930 can include an actuator element 933. The actuatorelement 933 can be controlled by the controller 350, so as toreciprocate within the actuator body 931. The actuator element 933 canbe connected to an actuator rod 932. The actuator rod 932 can beconnected to the moving board 910 at a moving board connection 934. Theactuator rod 932 can reciprocate back and forth, i.e. up and down asillustrated by arrow 933′. By control of the controller 350, theactuator rod 932 can be positioned at a desired location in a “range” ofreciprocation.

The actuator itself 930 can use known technology so as to providereciprocation. The actuator 930 can include or be in the form of asolenoid that utilizes an electromagnet arrangement so as to controlposition of the actuator element 933. For example, the actuator element933 can include a plunger that is disposed within one or more coils inthe actuator body 931. Energization of such coils can be selectivelyperformed so as to control the position of the actuator element 933.Other arrangements can be utilized so as to provide reciprocation of theactuator element 933. For example, a rack and pinion arrangement mightbe utilized. For example, the actuator element 933 can include a rack ofgears. The actuator body 931 can include a pinion gear, driven by amotor, that engages with the rack of gears. The controller 350 cancontrol rotation of the pinion gear by control of the motor—and as aresult, control reciprocation of the actuator element 933. Othermechanical arrangements can be utilized such that the controller 350 cancontrol reciprocation of the actuator element 933. Accordingly, suchcontrol of the actuator element 933 provides control of reciprocation ofthe actuator rod 932 and the moving board 910.

As shown in FIG. 41, the communication assembly 840 includes atransceiver cable board 901, the moving board 910, and an antenna cableboard 920. Each of the boards 901, 910, 920 can be constructed ofinsulating material. The transceiver cable board 901 includes conductivepads. The conductive pads on the transceiver cable board 901 can includefirst pads 902. The first pads 902 can include pad 902A and pad 902B.The pad 902A can be connected to the transceiver via cable 843A. The pad902B can be connected to the transceiver via cable 843B.

The moving board 910 can also be provided with conductive pads. Themoving board 910 on a left side as shown in FIG. 41, can include secondpads 911. The second pads 911 can include pad 911A and pad 911B. Themoving board on the right side as shown in FIG. 41 can include thirdpads 915. The third pads 915 can include pad 915A and pad 915B. The pad911B can be connected (and in electrical communication) to the pad 915Bvia an internal wire 914. The pad 911A can be connected (and inelectrical communication) to the pad 915B via an internal wire 913.

The antenna cable board 920 can also be provided with conductive pads.The conductive pads of the antenna cable board 920 can include fourthpads 921. The fourth pads 921 can include pad 921A and pad 921B. The pad921A can be connected to the antenna 830 via wire 834A. The pad 921B canbe connected to the antenna 830 via wire 834B. As shown in FIG. 41, theantenna switch 900 is shown as an exploded view. That is, FIG. 41 showsthe boards 901, 910, and 920 separated for purposes of illustration andclarity. Accordingly, in operation of the antenna switch 900, the firstpads 902 can be positioned so as to be in contact with the second pads911. As shown in FIG. 41, the first pads 902 will maintain contact withthe second pads 911, respectively, regardless of the reciprocation ortravel position of the moving board 910. That is, regardless of thereciprocation position of the moving board, the pad 902A will be incontact with the pad 911A, and also the pad 902B will be in contact withthe pad 911B. Further, the pads 911 and 902 can be constructed ofmaterial such that the pads may slide easily relative to each other.

In operation of the antenna switch 900, the third pads 915 can bepositioned so as to be in contact with a selected pair of the fourthpads 921. That is, in the particular reciprocation position of FIG. 41,the pad 915A will be in contact with the pad 921A. The pad 915B will bein contact with the pad 921B. As a result, the transceiver 941 will bein electrical contact with the antenna 830. Accordingly, the transceiver941 can input and output data to the antenna 830, as well as to energizethe antenna 830.

As shown in FIG. 41, the moving board 910 can move downwardly from theposition illustrated. Accordingly, as the moving board 910 movesdownwardly, contact between the third pads 915 and the pads 921A and921B will be lost. In other words, the third pads 915 will,respectively, no longer be aligned the pads 921A and 921B. Accordingly,the transceiver 841 wi11 no longer be in contact with the antenna 830.

As the moving board 910 moves downwardly, the third pads 915 willselectively be in contact with pairs of the fourth pads 921 that areconnected to either second antenna 830′ or third antenna 830″.Accordingly, based on position of the moving board 910 as itreciprocates up and down as shown in FIG. 41, the controller 350 cancontrol which antenna the transceiver 841 is connected to. Accordingly,upon the moving board 910 being positioned in a lower position, thethird pads 915 will be connected to the third antenna 830″. Morespecifically, the pad 915A will be connected to the pad 921E. The pad915B will be connected to the pad 921F. Accordingly, connection betweenthe transceiver 841 and the third antenna 830″ will be provided.Accordingly, the moving board 910 can be reciprocated as desired so asto connect the transceiver 841 with the desired antenna 830. Thus, thethird pads 915A, 915B can also be selectively connected to the pads921C, 921D, respectively.

The antenna switch 900 of FIG. 41 is a physical switch—in that theantenna switch 900 utilizes moving parts so as to control which antenna830 the transceiver 841 is connected to. In embodiments, othermechanisms can be utilized so as to control which antenna 830 isconnected to the transceiver 841. For example, solid-state technologycan be utilized in such arrangement. For example, respective electricalpathways between the transceiver 841 and each antenna can includematerials that constrain or prevent the flow of electricity and/or data.For example, respective electrical pathways between the transceiver 841can include one or more MOSFETs (Metal Oxide Semiconductor Field EffectTransistor). The controller 350 can control the MOSFET so as to controlthe electrical flow, through the various pathways, between thetransceiver 841 and the antennas 830. Other arrangements can be utilizedso as to selectively connect the transceiver 841 to an antenna 830 asdesired.

FIG. 42 is a flowchart showing additive vessel processing, in accordancewith at least one embodiment of the disclosure. More specifically, FIG.42 illustrates processing that can be used to selectively providecommunication between the transceiver 841 and an antenna 330.

As shown in FIG. 42, the process starts in step 770 and passes to step771. In step 771, the controller 350 identifies that base cover 317 hasbeen placed upon the dispensing assembly (from a removed disposition).As reflected at 771′, other events could be identified by the controllerto initiate processing. Then in step 772, the controller assignsvariable: Antenna #<==1. Then, in step 773, the controller controls theantenna switch 900 to change setting to Antenna [Antenna #], so as todictate which antenna the transceiver 841 communicates with.

Then, in step 774, the controller interfaces with the transceiver toinput data from the transceiver (i.e. processing is performed tointerrogate the vessel, via the transceiver, that is in communicationwith the connected antenna). Then, the process passes to step 775. Instep 775, the controller assigns variable: Antenna #<==(Antenna #+1).Then, the controller determines if Antenna #>3. If no, the processpasses back to step 773. As reflected at 778, such processing indicatesthat there is a further pod to interrogate and the controller advancesto interrogate the next vessel in sequence. On the other hand, a yes maybe rendered in step 776. Such reflects that all the vessels have beeninterrogated (777). Accordingly, the process passes to step 777′, andthe process ends. As reflected at 774′ of FIG. 42, in step 774, thetransceiver 841 performs processing to interface with the currentlyconnected antenna (and the particular pod/tag to which such antenna isin communication). In such processing, subroutine 780 of FIG. 43 can beperformed by the transceiver.

Accordingly, FIG. 43 is a flowchart showing processing in which thetransceiver performs processing to interface with the currentlyconnected antenna (and the particular pod/tag to which such antenna isin communication). The process starts in step 780 and passes to step782. In step 782, the transceiver attempts to interface with the vessel(via the currently connected transceiver antenna). A determination ismade of whether the interface was successful. If no, then the processpasses to step 784. In step 784, transceiver generates data indicatingthat current vessel “not found” and outputs such data to the controllerand/or outputs a communication to user.

On the other hand, a yes may be rendered in step 782. Accordingly, theprocess passes to step 783. In step 783, the transceiver generates dataindicating that current vessel “found” and communicates same to thecontroller. Then, in step 785, the controller performs vessel interfaceprocessing for the vessel that is currently energized (i.e. data ispassed between the controller and the tag antenna (via the transceiverand switch). In such processing, the subroutines of step 512 (FIG. 25)can be called upon, for example. Accordingly, data can be transferredbetween the controller and the tag of the vessel/pod. The tag can be anRFID tag. Then, in step 786, the controller determines if interrogationof the current vessel or pod is complete. Once complete, i.e. yes, theprocess passes to step 787. In step 787, the process returns to FIG. 42(step 775 of FIG. 42).

To describe related features further, the beverage apparatus 300 caninclude a transceiver 841 and a selection portion (or antenna switch),such as the antenna switch 900 shown in FIG. 37. The beverageapparatus/bottle can include a first antenna 830 and a second antenna830′.

A first electronic tag 410 (see FIG. 18 and FIG. 23) can be disposed ona first pod, and the first electronic tag can be an RFID tag. The firstelectronic tag 410 can include a first tag antenna 412 that interfaceswith the first antenna 830. A second electronic tag 410 can be disposedon a second pod, and the second electronic tag 410 can be a further RFIDtag. The second electronic tag 410 can include a second tag antenna 412that interfaces with the second antenna 830′ (FIG. 37).

The selection portion 900, e.g. antenna switch 900, can performprocessing including performing in sequence or selectively: (a)energizing the first antenna 830 to provide communication, includingdownloading or transmitting data, with the first electronic tag via thefirst antenna 830 generating a carrier wave that energizes the firstelectronic tag; and (b) energizing the second antenna 830′ to providecommunication, including downloading or transmitting data, with thesecond electronic tag via the second antenna 830′ generating a furthercarrier wave that energizes the second electronic tag of the second podor vessel. Thus, data can be transmitted between the transceiver 841 andan RFID tag of a pod. Accordingly, the particular pod that thetransceiver 841 communicates with can depend on the antenna 830/antenna412 pair that is energized. The selection portion 900 can be controlledby a controller of the beverage apparatus.

To describe further, in some embodiments of the disclosure, neither anRFID tag (on a pod or vessel) nor an antenna of the RFID tag is providedwith its own power source. For example, the RFID tag 410 and antenna412, shown in FIG. 23, may not be provided with a power source. Rather,the antenna 412 of the RFID tag (and RFID tag) can be energized by anenergy wave, such energy wave being generated by an antenna 830 (FIG.37) of the bottle/beverage apparatus. The energy wave can be a carrierwave. Thus, an antenna 412 of the RFID tag 410 (on a pod) can be poweredby the energy wave or carrier wave emitted by the antenna 830, forexample. In other words, the RFID tag 410 can be passive. However, it isappreciated that in other embodiments the RFID tag on the pod/vessel andthe antenna of the RFID tag can be powered. That is, an RFID tag, whichis mounted on a pod, can be active. An RFID tag that is powered may belarger in size and more costly than an RFID tag that is not powered.

Known RFID technology can be utilized in the embodiments describedherein, such as known technology can be used to afford the communicationor communication protocol between two communicating antennas thatcommunicate using RFID technology or other communication technology.

According to principles of the disclosure, processing can be performedso as to limit or constrain data transmission between a receiver 841 andan antenna 830. In accordance with at least one embodiment of thedisclosure, the controller 350 can detect and communicate with a tag (ona vessel) only when the pod is fully inserted into the particularreceptacle or bay. Accordingly, processing may be provided to rejecttags that are placed in nearby (radial distance) or tags are not fullyinserted (exile distance).

In accordance with an aspect of the processing, signal strength betweenthe transceiver 841 and the antenna 830 can fall off or reduce notablyas the tag moves from the center of the antenna in some arrangements. Anapproximation of this effect is shown in the plot 4400 of FIG. 44. Thatis, FIG. 44 is a diagram illustrating signal strength as it relates toradial distance. For example, with a particular arrangement, a tag canbe rejected beyond a 2-3 mm from center position. The graph 4400 is forpurposes of illustration and it should be appreciated that the magnitudeof parameters and particular shape will vary depending on the particulargeometry of the bottle, for example. Accordingly, FIG. 44 illustratessignal strength effect based on radial distance. There can be a similareffect with axial distance. FIG. 45 is a diagram illustrating signalstrength as it relates to axial distance. In the plot 4500, of FIG. 45,distance 0 corresponds to the antenna plane, negative values are insidethe unit (bottle), and positive values extend outward from the base. Asillustrated by the plot 4400 and the plot 4500, signal strength can varybased on position of a pod and attached RFID tag vis-à-vis the structureof the beverage apparatus or bottle. Accordingly, attributes of thesignal strength can be utilized by the controller 350 and/or transceiver841 so as to limit transmission between an RFID tag of a pod and thetransceiver/controller. For example, once the signal strength fallsbelow some predetermined threshold, communication between thetransceiver and the RFID tag of the pod can be disabled. Otherattributes of the communication between the transceiver and the RFID tagof the pod can also be utilized. For example, gain attributes and signalstrength of communications with the RFID tag can be utilized so as torequire particular attributes, i.e. in that such particular attributescan be indicative of a properly positioned pod within the beverageapparatus.

In various processing described herein and illustrated by flowcharts orotherwise described, variables can be used in various processes. Suchprocesses can include routines, subroutines, and steps, for example. Thevarious variables can be passed between processes as may be needed inaccord with the instructions provided to the ACP (apparatus computerprocessor). The various variables can be global variables that areavailable to the various processes, such as between a calling processand a subroutine, for example.

In accordance with one or more embodiments, a linear capacitive sensingstrip, or other liquid level reader may be mounted within or adjacent tothe chamber 316 of the beverage apparatus or bottle 300 within which aconsumable liquid may be stored (e.g., retained, contained, etc.). Thelinear capacitive sensing strip, or other liquid level reader may beconfigured to determine the level, volume, or quantity (e.g., theamount) of liquid consumable in the bottle 300 at any given time. Assuch, data about the consumable liquid in the chamber 316 of the bottle300 may be collected, analyzed, and/or communicated by the bottle 300(e.g., by a processor and/or other components of the bottle 300), andmade available to one or more user devices 106, storage systems ornetworks and the like. Related features are described in U.S.Publication 2016/0159632, now U.S. Pat. No. 9,932,217, which isincorporated herein by reference in its entirety. Such referenced(patent) is also referenced above. Features as described herein may beused in conjunction with the features described in such U.S. Pat. No.9,932,217.

Hereinafter, illustrative processing particulars are described. Suchparticulars are for purposes of illustration and may be varied asdesired. One dispense can correspond to 1 full reciprocation, up anddown, of the piston 405-390 for example, resulting in a dispense of 1mL, for example. To control the dispense amount, the ACP can vary traveldistance of the reciprocation of the piston 405-390 and/or vary thenumber of reciprocations of the piston, i.e. the reciprocation(s) up anddown of the vessel or pod 400. A dispense command can take on variousforms such as a predetermined dispense amount in mL that the ACPtranslates into movement of the piston, a number of dispenses that theACP translates into number of reciprocations, a set number ofreciprocations to be performed, a mass of liquid to dispense that theACP translate into reciprocations of the piston, etc. Dispenseprocessing can be “open loop” meaning that the action as controlled bythe ACP is independent of the actual output (although the actionperformed is crafted to generate a particular dispense amount). Forexample, one reciprocation of the piston down and up can be expected togenerate a dispense of 1 mL. Dispense processing can be “closed loop”meaning that the action, as controlled by the ACP, is monitored by asensor or feedback mechanism. For example, current required to performthe dispense can be monitored—and observed current can be mapped into acorresponding dispense amount. Alternatively, position of the plunger409 in the pod can be monitored, such as by a light source/sensor thatis positioned so as to detect position of the plunger. If feedbackreveals that the desired dispense wasn't obtained, further dispense canbe performed. Position of the plunger 409 can directly correspond toadditive dispensed from the pod. For example, the mass of a pod emptycan be 12 grams (g). The volume of additive in the pod can be 30 mL. Thedensity of the additive can be 1.02 g/mL. Accordingly, the mass of theadditive (in a full pod) can be 29.4 g. The additive can be dispensedbased on an assumption that 1 mL (milliliter) of additive will bedispensed by one reciprocation of piston 405-390. The “additive” in thepods can also be referred to as “concentrate”. The density of theadditive may be greater than water or less than water, depending on thecontent of the additive/concentrate.

Various patterns or schemes can be utilized such that the user caneffectively communicate with the beverage apparatus 300, as may bedesired. For example, one push of a particular button could dictate tothe beverage apparatus 300 that one additive should be released, whereas two quick pushes of the particular button could dictate that anotheradditive be dispensed. A push of a button and hold of that same buttoncould also be input by the controller, of the beverage apparatus, anddictate that a dispense should be performed.

Teachings of the incorporated by reference patent applications regardinguser interface can be utilized in conjunction with the teachingsdescribed herein. Other features of the above incorporated patentapplications can also be utilized in conjunction with the teachingsdescribed herein.

In embodiments of the disclosure, a computer processor of the beverageapparatus 300 may provide information to the user regarding metricsassociated with additives or other operation of the beverage apparatus300.

As described above, the beverage apparatus of the disclosure can includeone or more sensors to detect relative position of components of thebeverage apparatus. For example, a Hall effect sensor in conjunctionwith one or more magnets can be used to detect whether or not the basecover 317 is on the dispensing assembly 318. That is, a magnet may beprovided in the base cover 317 and a Hall effect sensor provided in thedispensing assembly 318, so as to sense proximity of the base cover 317.

As used herein, the indicia<==has been used to denote that a variable isassigned or “gets” a particular value. As used herein, the indicia · hasbeen used to indicate a multiplication operation—for example, 2·3=6.Also, the symbol x has been used to indicate a multiplication operation,for example, 2×3=6.

As described herein, the vessel or pod 400 can be provided with an RFIDtag 410 and the ACP 360 can communicate with the RFID tag via atransceiver or transceiver assembly 340, for example. However, it shouldbe appreciated that other communication technologies, protocols orcommunication channels may be used as desired. As described herein, areceptacle 390, pod 400, and other structure can extend though one ormore platforms, such as the platforms 308 and 309 shown in FIG. 22.Accordingly, suitable apertures or openings may be provided in suchplatforms so as to accommodate.

As described herein, the tag or RFID tag 410 can contain a wide varietyof data. The transceiver 340 can input data from the RFID tag and outputdata to the RFID tag. The RFID tag, or other data memory of the vessel400, can provide a data representation of a physical instance of the pod(to which the RFID tag is attached) and can provide a datarepresentation of a physical instance of the bottle or beverageapparatus 300. Accordingly, an event that is observed by the ACP 360,via sensors or other input, can be saved to the memory of the pod and/orto the apparatus database portion 370. For example, various historicaldata regarding use of the bottle and consumption of a user may bewritten in data form to the memory of the pod and/or to the apparatusdatabase portion 370. Accordingly, a log or record may be saved andmaintained.

Features as disclose herein may be described in context of particularunits or dimensions. It is appreciated that alternative units ordimensions can be used as desired. Additionally, conversion can beperformed between units or dimensions as may be desired. For example,processing is described herein as using units of degrees, such as 148°.Other units can be used, such as radians, for example.

As described above, the apparatus controller 350 can include anapparatus computer processor (ACP) 360. The ACP 360 may also bedescribed as an apparatus processing portion (APP) 360, a computerprocessor portion (CPP) 360, a computer processing portion (CPP) 360, orsimilar language. The ACP 360 can include or be in the form of a centralprocessing unit (CPU).

In this disclosure, quotation marks, such as with “pod mass adjustment”,have been used to enhance readability and/or to parse out a term orphrase for clarity.

All documents referenced herein are hereby incorporated by reference intheir entirety.

The terms dispersion, dispensing, dispense, and other similar terms havebeen used herein to convey manipulation of a liquid or other material.

It will be appreciated that features, elements and/or characteristicsdescribed with respect to one embodiment of the disclosure may bevariously used with other embodiments of the disclosure as may bedesired.

It will be appreciated that the effects of the present disclosure arenot limited to the above-mentioned effects, and other effects, which arenot mentioned herein, will be apparent to those in the art from thedisclosure and accompanying claims.

Although the preferred embodiments of the present disclosure have beendisclosed for illustrative purposes, those skilled in the art willappreciate that various modifications, additions and substitutions arepossible, without departing from the scope and spirit of the disclosureand accompanying claims.

It is appreciated that the various components of embodiments of thedisclosure may be made from any of a variety of materials including, forexample, plastic, plastic resin, nylon, composite material, foam,rubber, wood, metal, and/or ceramic, for example, or any other materialas may be desired.

A variety of production techniques may be used to make the apparatusesas described herein. For example, suitable injection molding and othermolding techniques and other manufacturing techniques might be utilized.Also, the various components of the apparatuses may be integrallyformed, as may be desired, in particular when using molding constructiontechniques. Also, the various components of the apparatuses may beformed in pieces and connected together in some manner, such as withsuitable adhesive and/or heat bonding.

The various apparatuses and components of the apparatuses, as describedherein, may be provided in various sizes and/or dimensions, as desired.

It will be understood that when an element or layer is referred to asbeing “on” another element or layer, the element or layer can bedirectly on another element or layer or intervening elements or layers.In contrast, when an element is referred to as being “directly on”another element or layer, there are no intervening elements or layerspresent.

It will be understood that when an element or layer is referred to asbeing “onto” another element or layer, the element or layer can bedirectly on another element or layer or intervening elements or layers.Examples include “attached onto”, secured onto”, and “provided onto”. Incontrast, when an element is referred to as being “directly onto”another element or layer, there are no intervening elements or layerspresent. As used herein, “onto” and “on to” have been usedinterchangeably.

It will be understood that when an element or layer is referred to asbeing “attached to” another element or layer, the element or layer canbe directly attached to the another element or layer or interveningelements or layers. In contrast, when an element is referred to as being“attached directly to” another element or layer, there are nointervening elements or layers present. It will be understood that suchrelationship also is to be understood with regard to: “secured to”versus “secured directly to”; “provided to” versus “provided directlyto”; and similar language.

As used herein, the term “and/or” includes any and all combinations ofone or more of the associated listed items. It will be understood that,although the terms first, second, third, etc., may be used herein todescribe various elements, components, regions, layers and/or sections,these elements, components, regions, layers and/or sections should notbe limited by these terms. These terms are only used to distinguish oneelement, component, region, layer or section from another region, layeror section. Thus, a first element, component, region, layer or sectioncould be termed a second element, component, region, layer or sectionwithout departing from the teachings of the present disclosure.

Spatially relative terms, such as “lower”, “upper”, “top”, “bottom”,“left”, “right” and the like, may be used herein for ease of descriptionto describe the relationship of one element or feature to anotherelement(s) or feature(s) as illustrated in the drawing figures. It willbe understood that spatially relative terms are intended to encompassdifferent orientations of structures in use or operation, in addition tothe orientation depicted in the drawing figures. For example, if adevice or apparatus in the drawing figures is turned over, elementsdescribed as “lower” relative to other elements or features would thenbe oriented “upper” relative the other elements or features. Thus, theexemplary term “lower” can encompass both an orientation of above andbelow. The device may be otherwise oriented (rotated 90 degrees or atother orientations) and the spatially relative descriptors used hereinshould be interpreted accordingly.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the disclosure.As used herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

Unless otherwise defined, all terms (including technical and scientificterms) used herein have the same meaning as commonly understood by oneof ordinary skill in the art to which this disclosure belongs. It willbe further understood that terms, such as those defined in commonly useddictionaries, should be interpreted as having a meaning that isconsistent with their meaning in the context of the relevant art andwill not be interpreted in an idealized or overly formal sense unlessexpressly so defined herein.

Any reference in this specification to “one embodiment,” “anembodiment,” “example embodiment,” etc., means that a particularfeature, structure, or characteristic described in connection with theembodiment is included in at least one embodiment of the disclosure. Theappearances of such phrases in various places in the specification arenot necessarily all referring to the same embodiment. Further, asotherwise noted herein, when a particular feature, structure, orcharacteristic is described in connection with any embodiment, it issubmitted that it is within the purview of one skilled in the art toeffect and/or use such feature, structure, or characteristic inconnection with other ones of the embodiments.

Embodiments are also intended to include or otherwise cover methods ofusing and methods of manufacturing any or all of the elements disclosedabove.

As otherwise described herein, it is appreciated that a feature of oneembodiment of the disclosure as described herein may be used inconjunction with features of one or more other embodiments as may bedesired.

As used herein, “data” and “information” have been used interchangeably.

Any motorized structure or other mechanical structure as describedherein may utilize gears, linkages, sprocket with chain, or other knownmechanical arrangement so as to transfer requisite motion and/or energy.

Hereinafter, further aspects of implementation of the systems andmethods of the disclosure will be described.

As described herein, at least some embodiments of the system of thedisclosure and various processes, of embodiments, are described as beingperformed by one or more computer processors, i.e. processors. Such oneor more computer processors may be in the form of a “processingmachine,” i.e. a tangibly embodied machine. As used herein, the term“processing machine” is to be understood to include at least oneprocessor that uses at least one memory. The at least one memory storesa set of instructions. The instructions may be either permanently ortemporarily stored in the memory or memories of the processing machine.The processor executes the instructions that are stored in the memory ormemories in order to process data. The set of instructions may includevarious instructions that perform a particular task or tasks, such asany of the processing as described herein. Such a set of instructionsfor performing a particular task may be described as a program, softwareprogram, code or simply software.

As noted above, the processing machine, which may be constituted, forexample, by the particular system and/or systems described above, canexecute the instructions that are stored in the memory or memories toprocess data. This processing of data may be in response to commands bya user or users of the processing machine, in response to previousprocessing, in response to a request by another processing machineand/or any other input, for example. As noted above, the machine used toimplement the disclosure may be in the form of a processing machine. Theprocessing machine may also utilize (or be in the form of) any of a widevariety of other technologies including a special purpose computer, acomputer system including a microcomputer, mini-computer or mainframefor example, a programmed microprocessor, a micro-controller, aperipheral integrated circuit element, a CSIC (Consumer SpecificIntegrated Circuit) or ASIC (Application Specific Integrated Circuit) orother integrated circuit, a logic circuit, a digital signal processor, aprogrammable logic device such as a FPGA, PLD, PLA or PAL, or any otherdevice or arrangement of devices, or apparatus that is capable ofimplementing the steps of the processes of the disclosure.

The processing machine used to implement the disclosure may utilize asuitable operating system. Thus, embodiments of the disclosure mayinclude a processing machine running the Windows 10 operating system,the Windows 8 operating system, Microsoft Windows™ Vista™ operatingsystem, the Microsoft Windows™ XP™ operating system, the MicrosoftWindows™ NT™ operating system, the Windows™ 2000 operating system, theUnix operating system, the Linux operating system, the Xenix operatingsystem, the IBM AIX™ operating system, the Hewlett-Packard UX™ operatingsystem, the Novell Netware™ operating system, the Sun MicrosystemsSolaris™ operating system, the OS/2™ operating system, the BeOS™operating system, the Macintosh operating system, the Apache operatingsystem, an OpenStep™ operating system or another operating system orplatform.

It is appreciated that in order to practice the method of the disclosureas described above, it is not necessary that the processors and/or thememories of the processing machine be physically located in the samegeographical place. That is, each of the processors and the memoriesused by the processing machine may be located in geographically distinctlocations and connected so as to communicate in any suitable manner.Additionally, it is appreciated that each of the processor and/or thememory may be composed of different physical pieces of equipment.Accordingly, it is not necessary that the processor be one single pieceof equipment in one location and that the memory be another single pieceof equipment in another location. That is, it is contemplated that theprocessor may be two pieces of equipment in two different physicallocations. The two distinct pieces of equipment may be connected in anysuitable manner. Additionally, the memory may include two or moreportions of memory in two or more physical locations.

To explain further, processing is described above can be performed byvarious components and various memories. However, it is appreciated thatthe processing performed by two distinct components as described abovemay, in accordance with a further embodiment of the disclosure, beperformed by a single component. Further, the processing performed byone distinct component as described above may be performed by twodistinct components. In a similar manner, the memory storage performedby two distinct memory portions as described above may, in accordancewith a further embodiment of the disclosure, be performed by a singlememory portion. Further, the memory storage performed by one distinctmemory portion as described above may be performed by two memoryportions.

Further, as also described above, various technologies may be used toprovide communication between the various processors and/or memories, aswell as to allow the processors and/or the memories of the disclosure tocommunicate with any other entity; i.e., so as to obtain furtherinstructions or to access and use remote memory stores, for example.Such technologies used to provide such communication might include anetwork, the Internet, Intranet, Extranet, LAN, an Ethernet, or anyclient server system that provides communication, for example. Suchcommunications technologies may use any suitable protocol such asTCP/IP, UDP, or OSI, for example.

A set of instructions can be used, in the processing as describedherein, on a processing machine, for example. The set of instructionsmay be in the form of a program or software. The software may be in theform of system software or application software, for example. Thesoftware might also be in the form of a collection of separate programs,a program module within a larger program, or a portion of a programmodule, for example. The software used might also include modularprogramming in the form of object oriented programming. The softwaretells the processing machine what to do with the data being processed.

Further, it is appreciated that the instructions or set of instructionsused in the implementation and operation of apparatus of the disclosuremay be in a suitable form such that the processing machine may read theinstructions. For example, the instructions that form a program may bein the form of a suitable programming language, which is converted tomachine language or object code to allow the processor or processors toread the instructions. That is, written lines of programming code orsource code, in a particular programming language, are converted tomachine language using a compiler, assembler or interpreter. The machinelanguage is binary coded machine instructions that are specific to aparticular type of processing machine, i.e., to a particular type ofcomputer, for example. The computer understands the machine language.

A suitable programming language may be used in accordance with thevarious embodiments of the disclosure. Illustratively, the programminglanguage used may include assembly language, Ada, APL, Basic, C, C++,COBOL, dBase, Forth, Fortran, Java, Modula-2, Pascal, Prolog, REXX,Visual Basic, and/or JavaScript, for example. Further, it is notnecessary that a single type of instructions or single programminglanguage be utilized in conjunction with the operation of the systemsand methods of the disclosure. Rather, any number of differentprogramming languages may be utilized as is necessary or desirable.

Also, the instructions and/or data used in the practice of thedisclosure may utilize any compression or encryption technique oralgorithm, as may be desired. An encryption module might be used toencrypt data. Further, files or other data may be decrypted using asuitable decryption module, for example.

As described above, the disclosure may illustratively be embodied in theform of a processing machine, including a computer or computer system,for example, that includes at least one memory. It is to be appreciatedthat the set of instructions, i.e., the software for example, thatenables the computer operating system to perform the operationsdescribed above may be contained on any of a wide variety of media ormedium, as desired. Further, the data that is processed by the set ofinstructions might also be contained on any of a wide variety of mediaor medium. That is, the particular medium, i.e., the memory in theprocessing machine, utilized to hold the set of instructions and/or thedata used in practice of the disclosure may take on any of a variety ofphysical forms or transmissions, for example. Illustratively, as alsodescribed above, the medium may be in the form of paper, papertransparencies, a compact disk, a DVD, an integrated circuit, a harddisk, a floppy disk, an optical disk, a magnetic tape, a RAM, a ROM, aPROM, a EPROM, a wire, a cable, a fiber, communications channel, asatellite transmissions or other remote transmission, as well as anyother medium or source of data that may be read by the processors of thedisclosure. Further, the memory or memories used in the processingmachine that implements the disclosure may be in any of a wide varietyof forms to allow the memory to hold instructions, data, or otherinformation, as is desired. Thus, the memory might be in the form of adatabase to hold data. The database might use any desired arrangement offiles such as a flat file arrangement or a relational databasearrangement, for example.

In the systems and methods of the disclosure, a variety of “userinterfaces” may be utilized to allow a user to interface with theprocessing machine or machines that are used to implement thedisclosure. As used herein, a user interface includes any hardware,software, or combination of hardware and software used by the processingmachine that allows a user to interact with the processing machine. Auser interface may be in the form of a dialogue screen for example. Auser interface may also include any of a mouse, touch screen, keyboard,voice reader, voice recognizer, dialogue screen, menu box, list,checkbox, toggle switch, a pushbutton, light, or any other device thatallows a user to receive information regarding the operation of theprocessing machine as it processes a set of instructions and/or providethe processing machine with information. Accordingly, the user interfaceis any device that provides communication between a user and aprocessing machine. The information provided by the user to theprocessing machine through the user interface may be in the form of acommand, a selection of data, or some other input, for example.

As discussed above, a user interface can be utilized by the processingmachine that performs a set of instructions such that the processingmachine processes data for a user. The user interface is typically usedby the processing machine for interacting with a user either to conveyinformation or receive information from the user. However, it should beappreciated that in accordance with some embodiments of the systems andmethods of the disclosure, it is not necessary that a human useractually interact with a user interface used by the processing machineof the disclosure. Rather, it is also contemplated that the userinterface of an apparatus of the disclosure might interact, i.e., conveyand receive information, with another processing machine, rather than ahuman user. Accordingly, the other processing machine might be describedas a user. Further, it is contemplated that a user interface utilized inthe systems and methods of the disclosure may interact partially withanother processing machine or processing machines, while alsointeracting partially with a human user.

Features are disclosed in the following disclosure.

According to principles of the disclosure, in an embodiment 1A, abeverage apparatus can be hand-holdable by a user of the beverageapparatus to be portable, and the beverage apparatus can comprise: (A) abeverage chamber housing that includes a chamber, and the chamberstoring a consumable liquid in the chamber; (B) a dispensing assemblythat includes a first receptacle and second receptacle, and (a) thefirst receptacle for retaining a first vessel, and the first vesselincluding a first electronic tag and containing a first additive, (b)the second receptacle for retaining a second vessel, and the secondvessel including a second electronic tag and containing a secondadditive; and (c) the dispensing assembly operatively controllable by acontroller to (a) output the first additive from the first vessel intothe consumable liquid, and (b) output the second additive from thesecond vessel into the consumable liquid; (C) an apparatus computerprocessor (ACP); (D) an apparatus database portion that includesinstructions that are performed by the ACP in operation of the beverageapparatus; (E) a first antenna that is associated with the firstreceptacle, and the first antenna for transferring data with the firstelectronic tag; (F) a second antenna that is associated with the secondreceptacle, and the second antenna for transferring data with the secondelectronic tag; (G) a transceiver that performs processing of data, andthe transceiver in communication with the ACP; and the processing ofdata including: (a) the transceiver communicating with the first antennato transfer data with the second antenna, and (b) the transceivercommunicating with the first antenna to transfer data with the secondantenna, and (H) an antenna switch controllable to selectively connectthe transceiver to (a) the first antenna for the ACP to transfer datawith the first antenna, and (b) the second antenna for the ACP totransfer data with the second antenna.

An embodiment 2A can include the features of the embodiment 1A in whichthe antenna switch being controllable includes the antenna switch beingcontrollable by the ACP to selectively connect the transceiver to thefirst antenna and the second antenna.

An embodiment 3A can include the features of the embodiment 2A in whichthe ACP being wired to the antenna switch to provide communicationbetween the ACP and the antenna switch.

An embodiment 4A can include the features of the embodiment 1A in whichfurther including a support platform, and the support platformsupporting the first antenna and the second antenna.

An embodiment 5A can include the features of the embodiment 4A in whichthe antenna switch wired to the first antenna, and the antenna switchwired to the second antenna.

An embodiment 6A can include the features of the embodiment 4A in whichthe first antenna includes a first loop structure that is in the shapeof a loop, and the second antenna includes a second loop structure thatis in the shape of a loop.

An embodiment 7A can include the features of the embodiment 6A in whichthe support platform including: (a) a first receptacle aperture forsupporting the first receptacle, the first antenna positioned about thefirst receptacle aperture, and (b) a second receptacle aperture forsupporting the second receptacle, the second antenna positioned aboutthe second receptacle aperture.

An embodiment 8A can include the features of the embodiment 7A in whichthe first antenna positioned about the first receptacle apertureincluding the first loop structure, of the first antenna, substantiallyencircling the first receptacle aperture; and (a) the second antennapositioned about the second receptacle aperture including the secondloop structure, of the second antenna, substantially encircling thesecond receptacle aperture.

An embodiment 9A can include the features of the embodiment 8A in whichthe first antenna at least 80% encircling the first receptacle aperture,and the second antenna at least 80% encircling the second receptacleaperture.

An embodiment 10A can include the features of the embodiment 9A in whichthe first antenna concentric with the first receptacle aperture; and thesecond antenna concentric with the second receptacle aperture.

An embodiment 11A can include the features of the embodiment 1A in whichthe transceiver includes an RFID transceiver.

An embodiment 12A can include the features of the embodiment 1A in whichbeverage apparatus further including the first vessel and the secondvessel.

An embodiment 13A can include the features of the embodiment 1A in whichthe dispensing assembly including: (a) a first valve associated with thefirst receptacle, and the first additive being dispensed into theconsumable liquid through the first valve; and (b) a second valveassociated with the second receptacle, and the second additive beingdispensed into the consumable liquid through the second valve.

An embodiment 14A can include the features of the embodiment 13A inwhich the first valve is a one-way valve, and the second valve is aone-way valve.

An embodiment 15A can include the features of the embodiment 1A in whichthe beverage apparatus further including a third receptacle forretaining a third vessel that contains a third additive.

According to principles of the disclosure, in an embodiment 1B, abeverage apparatus can be hand-holdable by a user of the beverageapparatus so as to be portable, and the beverage apparatus can comprise:(A) a beverage chamber housing that includes a chamber, and the chamberstoring a consumable liquid in the chamber; (B) a dispensing assemblythat includes a first receptacle and second receptacle, (C) a firstvessel that includes a first electronic tag and contains a firstadditive, and the first receptacle retaining the first vessel, and (D) asecond vessel that includes a second electronic tag and contains asecond additive, and the second receptacle retaining the second vessel;and the dispensing assembly operatively controllable by a controller to(a) output the first additive from the first vessel into the consumableliquid, and (b) output the second additive from the second vessel intothe consumable liquid; (E) an apparatus computer processor (ACP); (F) anapparatus database portion that includes instructions that are performedby the ACP in operation of the beverage apparatus; (G) a first antennathat is associated with the first receptacle, and the first antenna fortransferring data with the first electronic tag; (H) a second antennathat is associated with the second receptacle, and the second antennafor transferring data with the second electronic tag; (I) a transceiverthat performs processing of data, and the transceiver in communicationwith the ACP; and the processing of data including: (a) the transceiverinterfacing with the first antenna to provide first data transfer, and(b) the transceiver interfacing with the second antenna to providesecond data transfer, and (J) a selection portion that performscontrolling to control (a) the first data transfer, and (b) the seconddata transfer.

An embodiment 2B can include the features of the embodiment 1B in whichthe controlling performed by the selection portion including: (a)energizing the first antenna to provide communication, via thetransceiver and first antenna, between the ACP and the first electronictag; and (b) energizing the second antenna to provide communication, viathe transceiver and second antenna, between the ACP and the secondelectronic tag.

An embodiment 3B can include the features of the embodiment 2B in whichthe energizing the first antenna is performed at a different time thanthe energizing the second antenna.

An embodiment 4B can include the features of the embodiment 2B in whichthe controlling including the selection portion toggling betweenenergizing the first antenna and energizing the second antenna, so as tomutually exclusively energize the first antenna and the second antenna.

An embodiment 5B can include the features of the embodiment 4B in whichthe ACP interfaces with the selection portion to perform thecontrolling, such that that the ACP controls whether the first antennaor the second antenna is energized.

An embodiment 6B can include the features of the embodiment 1B in whichthe first antenna and the second antenna are in a common communicationcircuit with the transceiver such that the first antenna and the secondantenna share the common communication circuit; and (a) the firstantenna is associated with a first power supply; (b) the second antennais associated with a second power supply; and (c) the selection portionis controlled, by the ACP, to selectively energize the first powersupply or the second power supply, so as to selectively select eitherthe first antenna or the second antenna to provide communication.

An embodiment 7B can include the features of the embodiment 6B in whichthe selection portion toggles between energizing the first power supplyand the second power supply from a power source.

An embodiment 8B can include the features of the embodiment 1B in whichthe first electronic tag is an RFID tag, and the first electronic tagincludes a first tag antenna that interfaces with the first antenna; andthe second electronic tag is a further RFID tag, and the secondelectronic tag includes a second tag antenna that interfaces with thesecond antenna.

An embodiment 9B can include the features of the embodiment 1B in whichthe first antenna is circular in shape, and the second antenna iscircular in shape.

An embodiment 10B can include the features of the embodiment 8B in whichthe first antenna substantially surrounds the first vessel and thesecond antenna substantially surrounds the second vessel.

An embodiment 11B can include the features of the embodiment 1B in whichthe selection portion performing processing including observing that aphysical event has occurred with the beverage apparatus and, based onthe observing, performing in sequence: (a) energizing the first antennato provide communication, including downloading data, with the firstelectronic tag; and (b) energizing the second antenna to providecommunication, including downloading data, with the second electronictag.

An embodiment 12B can include the features of the embodiment 11B inwhich wherein the beverage apparatus includes a base cover that isremovably attached to a remainder of the beverage housing, and the basecover is removable by the user to insert the first vessel and the secondvessel; and the physical event includes at least one selected from thegroup consisting of: (a) the base cover being removed, and (b) the basecover being placed upon the beverage housing.

An embodiment 13B can include the features of the embodiment 12B inwhich the base cover including a magnet and the dispensing assemblyincluding a magnet sensor, and the magnet sensor configured to detectthe magnet.

An embodiment 14B can include the features of the embodiment 13B inwhich the base cover including three magnets, any of which areconfigured to activate the magnet sensor depending on a mounting angularorientation of the base cover on the beverage apparatus.

An embodiment 15B can include the features of the embodiment 1B in whichthe transceiver and/or the ACP processes data from the first antennaincluding: (a) determining an observed signal strength from the firstelectronic tag via the first antenna; (b) comparing the observed signalstrength to a threshold signal strength; (c) generating a determinationbased on determining that the observed signal strength is less than thethreshold signal strength; (d) ignoring the data from the first antennabased on the determination.

An embodiment 16B can include the features of the embodiment 1B in whichthe transceiver and/or the ACP processes data from the first antennaincluding: (a) determining an observed signal strength from the firstelectronic tag via the first antenna; (b) comparing the observed signalstrength to a threshold signal strength; (c) generating a determinationbased on determining that the observed signal strength is greater thanthe threshold signal strength; (d) processing the data from the firstantenna based on the determination.

An embodiment 17B can include the features of the embodiment 1B in whichthe selection portion is a switch that selectively (a) connects thetransceiver to the first antenna for the first data transfer, and (b)connects the transceiver to the second antenna for the second datatransfer.

An embodiment 18B can include the features of the embodiment 1B in whichwherein (a) the first electronic tag is adhesively attached to the firstvessel; and/or (b) the first electronic tag is integrated into a wall ofthe first vessel.

An embodiment 19B can include the features of the embodiment 1B in whichwherein (a) the first electronic tag is an RFID tag, and the firstelectronic tag includes a first tag antenna that interfaces with thefirst antenna, and (b) the second electronic tag is a further RFID tag,and the second electronic tag includes a second tag antenna thatinterfaces with the second antenna; and (A) the selection portionperforming processing including performing in sequence: (a) energizingthe first antenna to provide communication, including downloading data,with the first electronic tag via the first antenna generating a carrierwave that energizes the first electronic tag; and (b) energizing thesecond antenna to provide communication, including downloading data,with the second electronic tag via the second antenna generating afurther carrier wave that energizes the second electronic tag.

According to principles of the disclosure, in an embodiment 1C, abeverage apparatus can be hand-holdable by a user of the beverageapparatus so as to provide portability, and the beverage apparatus cancomprise: (A) a beverage chamber housing that includes a chamber, andthe container assembly storing a consumable liquid in the chamber; (B) atag that includes a tag memory portion (TMP) and a tag communicationelement; (C) a vessel that contains an additive to be dispensed into theconsumable liquid, and the vessel including a valve through which theadditive is dispensed, and the tag being affixed to the vessel; (D) adispensing assembly that includes: (a) an aperture, the aperturestructured to retain the vessel such that the vessel is removable; and(b) a dispense mechanism associated with the vessel, and the dispensemechanism operable to affect transfer of the additive from therespective vessel, through the valve, into the consumable liquid; (E) acontroller that includes: (a) a processer; (b) a database, and thedatabase including instructions implemented by the processor, and theprocessor configured to control the dispense mechanism and tocommunicate with the tag; and (c) a controller communication elementthat interfaces with the tag communication element to transmitcommunications between the processor and the tag; and (F) the processorconfigured to perform processing including: (a) identifying a change instate of the beverage apparatus; (b) adjusting value of a statevariable, based on the change in state, from a first value to a secondvalue; and (c) writing the second value, of the state variable, to theTMP of the tag.

An embodiment 2C can include the features of the embodiment 1C in whichthe processor configured to perform processing including: (a) inputtinga default dose from the tag; (b) determining a dispense amount, for adispense, based on the default dose; (c) controlling the dispensemechanism to dispense the dispense amount, of the additive, into theconsumable liquid; and (d) the adjusting value of the state variableincludes performing fill value processing, the fill value processingincluding: decrementing a fill value, which constitutes the first value,of the vessel based on the dispense amount to render an adjusted fillvalue, which constitutes the second value; and (e) the writing the statevariable to the TMP of the tag includes writing the second value to theTMP.

An embodiment 3C can include the features of the embodiment 2C in whichthe determining the dispense amount based on the default dose includes:comparing the dispense amount with the fill value to determine ifsufficient additive is available, in the vessel, to support thedispense.

An embodiment 4C can include the features of the embodiment 2C in whichthe determining a dispense amount for a dispense, based on the defaultdose further includes: adjusting the default dose based on a tastepreference coefficient (TPC) so as to generate an adjusted dispensevalue, and the processor using the adjusted dispense value as thedispense value.

An embodiment 5C can include the features of the embodiment 4C in whichthe adjusting the default dose based on the TPC includes the processormultiplying the default dose by the TPC to generate the adjusteddispense value.

An embodiment 6C can include the features of the embodiment 4C in whichthe processor configured to perform processing including: (a) comparingthe adjusted dispense value with a maximum dose of the additive todetermine if the adjusted dispense value is less than the maximum dose;and (b) determining that the adjusted dispense value is less than themaximum dose.

An embodiment 7C can include the features of the embodiment 6C in whichthe processor configured to perform processing including: (a) comparingthe adjusted dispense value with a minimum dose of the additive todetermine if the adjusted dispense value is more than the minimum dose;and (b) determining that the adjusted dispense value is more than theminimum dose.

An embodiment 8C can include the features of the embodiment 4C in whichthe processor configured to perform processing including: (a) inputtinga maximum dose of the additive from the tag; (b) comparing the adjusteddispense value with the maximum dose of the additive to determine if theadjusted dispense value is less than the maximum dose; and (c)determining that the adjusted dispense value is less than the maximumdose.

An embodiment 9C can include the features of the embodiment 4C in whichthe processor configured to perform processing including: (a) inputtinga minimum dose of the additive from the tag; (b) comparing the adjusteddispense value with the minimum dose of the additive to determine if theadjusted dispense value is more than the minimum dose; and (c)determining that the adjusted dispense value is more than the minimumdose.

An embodiment 10C can include the features of the embodiment 2C in whichthe perform fill value processing including retrieving the fill valuefrom the TMP.

An embodiment 11C can include the features of the embodiment 10C inwhich the performing fill value processing further including writing theadjusted fill value to the TMP to write over the fill value in the TMP.

An embodiment 12C can include the features of the embodiment 10C inwhich the processor performing further processing, for a furtherdispense, including: (a) retrieving the adjusted fill value, which waswritten to the TMP so as to be a new fill value, and (b) confirming thatthere is sufficient additive for the further dispense based on theretrieved adjusted fill value.

An embodiment 13C can include the features of the embodiment 1C in whichthe processor configured to perform processing including: (a) retrievingtag warning data from the tag; (b) retrieving profile warning data fromthe database; (c) comparing the tag warning data and the profile warningdata; and (d) determining that there is not a match between the tagwarning data and the profile warning data.

An embodiment 14C can include the features of the embodiment 1C in whichthe processor configured to perform processing including: (a) retrievingexpiry data from the tag, the expiry data including at least oneselected from the group consisting of (1) an expiration date, and (2) afill date and life duration; (b) determining, based on the expiry data,whether the vessel is or is not expired, to respectively indicativewhether the vessel is or is not suitable for use; and (c) determiningthat the vessel is not expired.

An embodiment 15C can include the features of the embodiment 1C in whichfurther including a light that is adjustable in color, and the lightexposed to the consumable liquid; and the processor configured toperform processing including: (a) retrieving light color data from thetag; (b) controlling the light to emit a predetermined color, based onthe light color data, in conjunction with operation of the dispensemechanism.

An embodiment 16C can include the features of the embodiment 1C in whichthe processor configured to communicate with the tag including: (a)encrypting information to be sent to the tag; and (b) the processordecrypting information received from the tag.

An embodiment 17C can include the features of the embodiment 1C in whichthe tag is an RFID tag that includes an integrated circuit, and the tagcommunication element is an antenna, and the controller communicationelement is a transceiver.

An embodiment 18C can include the features of the embodiment 1C in whichthe vessel constitutes a first vessel and, the tag constitutes a firsttag, and the beverage apparatus further including a second vessel thatis associated with a second tag that communicates with the controller toperform dispensing of a further additive in the further vessel.

According to principles of the disclosure, in an embodiment 1D, a methodcan include varying the composition of a consumable liquid in a beverageapparatus, the beverage apparatus being hand-holdable by a user of thebeverage apparatus, the beverage apparatus including an internal volumethat contains the consumable liquid, and the beverage apparatusincluding a vessel with a tag, and the vessel being removable andcontaining an additive. In the embodiment 1D, the method can include:(A) identifying, by the processor, a request for a dispense of anadditive contained in the vessel; (B) determining, by the processor, adispense amount for the dispense; (C) controlling, by the processor, adispense mechanism to dispense the dispense amount, of the additive,from the vessel into the consumable liquid; (D) identifying, by theprocessor, a change in state of the beverage apparatus; (E) adjusting,by the processor a value of a state variable, based on the change instate, from a first value to a second value; and (F) writing, by theprocessor, the second value, of the state variable, to the tag.

An embodiment 2D can include the features of the embodiment 1D in whichthe change in state of the beverage apparatus being the dispense of theadditive; and the state variable being a fill level, of additive, of thevessel.

An embodiment 3D can include the features of the embodiment 2D in whichthe adjusting value of the state variable from the first value to thesecond value is constituted by decrementing the first value, whichrepresents fill level before dispense, to the second value, whichrepresents fill level after the dispense.

An embodiment 4D can include the features of the embodiment 3D in whichthe tag including a tag memory portion (TMP) and an antenna thatprovides communication to the processor; and the beverage apparatusincludes a receiver that communicates with the antenna.

An embodiment 5D can include the features of the embodiment 4D in whichfurther including the processor inputting the first value from the TMP.

An embodiment 6D can include the features of the embodiment 5D in whichthe writing the second value, of the state variable, to the tagincludes: writing over the first value in the TMP so as update the firstvalue to the second value.

An embodiment 7D can include the features of the embodiment 6D in whichthe TMP including a data record with a field to store the fill level,and the update the first value to the second value is constituted byupdating the field with the second value.

An embodiment 8D can include the features of the embodiment 1D in whichthe state variable is maintained in a tag memory portion in the tag.

An embodiment 9D can include the features of the embodiment 1D in whichthe state variable is maintained in a container database portion in thebeverage container.

An embodiment 10D can include the features of the embodiment 1D in whichthe identifying a change in state includes an observed rapiddeceleration; (a) the first value is a no value; (b) the second value isa yes value, to reflect that the beverage apparatus has been dropped;and (c) the writing the second value to the tag includes writing thesecond value to a predetermined data field in the tag.

An embodiment 11D can include the features of the embodiment 1D in whichfurther including the processor: (a) communicating with the tag to readidentification data from a user data field of the tag; (b) based on areturned value, determining that the vessel has not been associated witha previous beverage apparatus.

An embodiment 12D can include the features of the embodiment 11D inwhich further including the processor: (a) retrieving identificationdata from a database portion of the beverage apparatus; and (b) writingthe identification data to a user data field in the tag so as toestablish an association of the beverage apparatus with the vessel.

An embodiment 13D can include the features of the embodiment 1D in whichfurther including the processor: (a) retrieving identification data froma database portion of the beverage apparatus; and (b) writing theidentification data to a user data field in the tag so as to uniquelyassociate the beverage apparatus with the vessel.

An embodiment 14D can include the features of the embodiment 1D in whichthe identifying a change in state includes identifying an elevatedtemperature; and (a) the first value reflects an acceptable operatingtemperature; (b) the second value reflects an unacceptable operatingtemperature; and (c) the writing the second value to the tag includeswriting the second value to a predetermined data field in the tag.

It will be readily understood by those persons skilled in the art thatthe present disclosure is susceptible to broad utility and application.Many embodiments and adaptations of the present disclosure other thanthose herein described, as well as many variations, modifications andequivalent arrangements, will be apparent from or reasonably suggestedby the present disclosure and foregoing description thereof, withoutdeparting from the substance or scope of the disclosure.

Accordingly, while the present disclosure has been described here indetail in relation to its exemplary embodiments, it is to be understoodthat this disclosure is only illustrative and exemplary of the presentdisclosure and is made to provide an enabling disclosure. Accordingly,the foregoing disclosure is not intended to be construed or to limit thepresent disclosure or otherwise to exclude any other such embodiments,adaptations, variations, modifications and equivalent arrangements.

What is claimed is:
 1. A beverage apparatus, the beverage apparatusbeing hand-holdable by a user of the beverage apparatus to be portable,the beverage apparatus comprising: a beverage chamber housing thatincludes a chamber, and the chamber storing a consumable liquid in thechamber; a dispensing assembly that includes a first receptacle and asecond receptacle, and the first receptacle for retaining a firstvessel, and the first vessel including a first electronic tag andcontaining a first additive, the second receptacle for retaining asecond vessel, and the second vessel including a second electronic tagand containing a second additive; and the dispensing assemblyoperatively controllable by a controller to (a) output the firstadditive from the first vessel into the consumable liquid in thechamber, and (b) output the second additive from the second vessel intothe consumable liquid in the chamber; an apparatus computer processor(ACP); an apparatus database portion that includes instructions that areperformed by the ACP in operation of the beverage apparatus, and thecontroller including the ACP and the apparatus database portion; a firstantenna that is associated with the first receptacle, and the firstantenna for transferring data with the first electronic tag; a secondantenna that is associated with the second receptacle, and the secondantenna for transferring data with the second electronic tag; atransceiver that performs processing of data, and the transceiver incommunication with the ACP; and the processing of data including: thetransceiver communicating with the first antenna to transfer data withthe first antenna, and the transceiver communicating with the secondantenna to transfer data with the second antenna, and an antenna switchcontrollable to selectively connect the transceiver to (a) the firstantenna for the ACP to transfer data with the first antenna, and (b) thesecond antenna for the ACP to transfer data with the second antenna. 2.The beverage apparatus of claim 1, the antenna switch being controllableincludes the antenna switch being controllable by the ACP to selectivelyconnect the transceiver to the first antenna and the second antenna. 3.The beverage apparatus of claim 2, the ACP being wired to the antennaswitch to provide communication between the ACP and the antenna switch.4. The beverage apparatus of claim 1, further including a supportplatform, and the support platform supporting the first antenna and thesecond antenna.
 5. The beverage apparatus of claim 4, the antenna switchwired to the first antenna, and the antenna switch wired to the secondantenna.
 6. The beverage apparatus of claim 4, the first antennaincludes a first loop structure that is in the shape of a loop, and thesecond antenna includes a second loop structure that is in the shape ofa loop.
 7. The beverage apparatus of claim 6, the support platformincluding: a first receptacle aperture for supporting the firstreceptacle, the first antenna positioned about the first receptacleaperture, and a second receptacle aperture for supporting the secondreceptacle, the second antenna positioned about the second receptacleaperture.
 8. The beverage apparatus of claim 7, the first antennapositioned about the first receptacle aperture including the first loopstructure, of the first antenna, substantially encircling the firstreceptacle aperture; and the second antenna positioned about the secondreceptacle aperture including the second loop structure, of the secondantenna, substantially encircling the second receptacle aperture.
 9. Thebeverage apparatus of claim 8, the first antenna at least 80% encirclingthe first receptacle aperture, and the second antenna at least 80%encircling the second receptacle aperture.
 10. The beverage apparatus ofclaim 9, the first antenna concentric with the first receptacleaperture; and the second antenna concentric with the second receptacleaperture.
 11. The beverage apparatus of claim 1, the transceiverincludes an RFID transceiver.
 12. The beverage apparatus of claim 1, thebeverage apparatus further including the first vessel and the secondvessel.
 13. The beverage apparatus of claim 1, the dispensing assemblyincluding: a first valve associated with the first receptacle, and thefirst additive being dispensed into the consumable liquid, in thechamber, through the first valve; and a second valve associated with thesecond receptacle, and the second additive being dispensed into theconsumable liquid, in the chamber, through the second valve.
 14. Thebeverage apparatus of claim 13, the first valve is a one-way valve, andthe second valve is a one-way valve.
 15. The beverage apparatus of claim1, the beverage apparatus further including a third receptacle forretaining a third vessel that contains a third additive.